Triple
T20045807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamma Tucanae |
E497553
|
entity |
| Predicate | usedAsReferencePoint |
P7051
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Gamma Tucanae, usedAsReferencePoint, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsReferencePoint Context triple: [Gamma Tucanae, usedAsReferencePoint, true]
-
A.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
B.
usesBasePoint
Indicates that one entity performs an operation or defines a structure by referencing or relying on a specific base point.
-
C.
usedAsLocationIn
Indicates that something serves as the setting or place where another event, action, or situation occurs.
-
D.
usedReferenceFrame
Indicates that one entity adopts or relies on another entity as the coordinate system or reference frame for describing positions, motions, or measurements.
-
E.
usedAsBasisFor
chosen
Indicates that one entity serves as the foundation, reference, or starting point upon which another entity is developed, derived, justified, or constructed.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632a5e888190ade41657ffd057f6 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.