Triple
T37105306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4179 Toutatis |
E918823
|
entity |
| Predicate | radarObservedBy |
P119853
|
FINISHED |
| Object | Arecibo Observatory |
—
|
NE NERFINISHED |
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: Arecibo Observatory | Statement: [4179 Toutatis, radarObservedBy, Arecibo Observatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarObservedBy Context triple: [4179 Toutatis, radarObservedBy, Arecibo Observatory]
-
A.
radarEquipment
Indicates that one entity is radar equipment used for detecting, tracking, or measuring objects relative to another entity.
-
B.
radarStationOperationalFrom
Indicates the time or date from which a radar station begins or began operating.
-
C.
radarType
Indicates the specific category or classification of radar associated with an entity.
-
D.
associatedRadar
Indicates that one entity is linked or connected to a specific radar system or radar-related resource.
-
E.
associatedObservatory
chosen
Indicates that an entity has a relationship with, or is linked to, a particular observatory, such as being operated by, observed at, or otherwise connected to it.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.