Triple
T32023951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pound–Rebka experiment |
E817767
|
entity |
| Predicate | detectorPosition |
P173131
|
FINISHED |
| Object | top of tower |
—
|
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: top of tower | Statement: [Pound–Rebka experiment, detectorPosition, top of tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectorPosition Context triple: [Pound–Rebka experiment, detectorPosition, top of tower]
-
A.
conePosition
Indicates the spatial position or placement of a cone relative to a reference frame or environment.
-
B.
determinedPosition
Indicates that one entity has established or calculated the specific position or location of another entity.
-
C.
positionInChamber
Indicates the specific location or role an entity holds within a particular chamber or assembly.
-
D.
positionObtainedBy
Indicates that a particular position or role is acquired, achieved, or secured through a specified action, process, or agent.
-
E.
farDetectorLocation
Indicates that one entity is located at or corresponds to the position of a far (distant) detector relative to another reference point or system.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4684000819090d1f2f28af40db9 |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:17 a.m.