Triple
T14439105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | subant |
E358040
|
entity |
| Predicate | hasChildElement |
P6882
|
FINISHED |
| Object | property |
—
|
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: property | Statement: [subant, hasChildElement, property]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildElement Context triple: [subant, hasChildElement, property]
-
A.
has child
chosen
Indicates that one entity is the parent of another entity, which is its child.
-
B.
hasChildOfHead
Indicates that an entity has, as a subordinate or component, another entity that is the child of its head element or primary governing part.
-
C.
hasChildCharacters
Indicates that one entity includes or is associated with other entities that are considered its child characters in a hierarchical or narrative structure.
-
D.
hasChildrenWith
Indicates that two entities share one or more biological or adopted children together.
-
E.
hasRootElement
Indicates that one entity is the primary or top-level element from which the structure or hierarchy of another entity originates.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914a45ec81909ab8ccf302047d7f |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.