Triple
T19132950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (55636) 2002 TX300 |
E468358
|
entity |
| Predicate | hasPhaseCoefficient |
P134532
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [(55636) 2002 TX300, hasPhaseCoefficient, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhaseCoefficient Context triple: [(55636) 2002 TX300, hasPhaseCoefficient, low]
-
A.
hasPhaseRelation
Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
-
B.
hasPhaseTransition
Indicates that an entity undergoes or exhibits a change from one physical phase or state of matter to another.
-
C.
phaseIndicatedBy
Indicates that a particular phase or stage is determined, signaled, or specified by a given indicator or reference.
-
D.
phaseUsed
Indicates that a particular phase, stage, or step is utilized or applied in carrying out an action, process, or relationship.
-
E.
phaseDifferenceDependsOn
Indicates that the phase difference between two signals or waves is determined by, or varies as a function of, another specified quantity or condition.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ea82f08190811ef35fbae744d1 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.