Triple
T8020893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mothers |
E186737
|
entity |
| Predicate | hasListingRules |
P2846
|
FINISHED |
| Object | disclosure requirements for emerging companies |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: disclosure requirements for emerging companies | Statement: [Mothers, hasListingRules, disclosure requirements for emerging companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListingRules Context triple: [Mothers, hasListingRules, disclosure requirements for emerging companies]
-
A.
hasListingAuthority
Indicates that an entity has the official power or permission to create, approve, or manage listings for another entity or resource.
-
B.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
isListing
Indicates that an entity functions as a listing, typically representing an item, service, or offering that is being presented, advertised, or made available.
-
D.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
E.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8d90488190b57d1e748e272061 |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.