Triple
T19831646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3(OH) |
E476473
|
entity |
| Predicate | hasParallaxMeasurements |
P126729
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [W3(OH), hasParallaxMeasurements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParallaxMeasurements Context triple: [W3(OH), hasParallaxMeasurements, yes]
-
A.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
B.
parallaxAccuracy
Indicates the degree of precision or reliability associated with a measured parallax value.
-
C.
hasMeasuredParameter
chosen
Indicates that an entity has a specific parameter that has been quantitatively measured or recorded.
-
D.
hasWellMeasuredDistances
Indicates that accurate and reliable distance measurements have been obtained between the related entities.
-
E.
parallax
Indicates the apparent shift in an object’s position relative to a background when observed from two different viewpoints or at two different times.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656ce68b48190aa25b29d0b6ea021 |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.