Triple
T33658419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dot3CollTable |
E862284
|
entity |
| Predicate | hasParentObject |
P199598
|
FINISHED |
| Object | dot3CollEntry |
—
|
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: dot3CollEntry | Statement: [dot3CollTable, hasParentObject, dot3CollEntry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentObject Context triple: [dot3CollTable, hasParentObject, dot3CollEntry]
-
A.
sometimesHasParent
Indicates that an entity has a particular parent entity in some, but not necessarily all, situations or contexts.
-
B.
hasParentMaterial
Indicates that one entity is derived from, formed in, or directly associated with another entity that serves as its original or underlying material.
-
C.
hasParentUnit
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
-
D.
hasParentAccordingToSource
Indicates that an entity is recorded as the parent of another entity according to a specified source or authority.
-
E.
hasFormerParent
Indicates that an entity was previously the parent of another entity but no longer holds that parental role or status.
- F. None of above. chosen
Provenance (4 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
| PDg | Predicate description generation | batch_69ff4818bb288190b4a27576fad18e23 |
completed | May 9, 2026, 2:43 p.m. |
Created at: May 1, 2026, 1:42 a.m.