Triple
T4887881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C. J. Cregg |
E109481
|
entity |
| Predicate | heightInUniverse |
P60425
|
FINISHED |
| Object | approximately 6 feet |
—
|
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: approximately 6 feet | Statement: [C. J. Cregg, heightInUniverse, approximately 6 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightInUniverse Context triple: [C. J. Cregg, heightInUniverse, approximately 6 feet]
-
A.
positionInCosmos
Indicates the spatial or hierarchical location of an entity within the broader structure of the cosmos or universe.
-
B.
heightInInches
Indicates that one entity has a specific height measured in inches.
-
C.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
D.
heightAboveSurroundings
Indicates that an entity’s vertical position or elevation is higher than that of its immediate surrounding area.
-
E.
highestWorld
Indicates that the subject entity occupies or is associated with the topmost or most elevated world, level, or realm within a defined hierarchy of worlds.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2e7b5c8190b8bf9d616dfa24f0 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:28 p.m.