Triple
T11317362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evpatoria RT-70 radio telescope |
E267999
|
entity |
| Predicate | hasObservationTarget |
P98477
|
FINISHED |
| Object | planets |
—
|
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: planets | Statement: [Evpatoria RT-70 radio telescope, hasObservationTarget, planets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservationTarget Context triple: [Evpatoria RT-70 radio telescope, hasObservationTarget, planets]
-
A.
hasObservation
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
B.
hasObservationMethod
Indicates that a particular method, technique, or procedure is used to perform or obtain an observation.
-
C.
hasObservationArea
Indicates that an entity possesses or includes a designated area from which observations or monitoring activities are conducted.
-
D.
isObservedOn
Indicates that a particular phenomenon, condition, or attribute is detected or recorded at a specific time, date, or occasion.
-
E.
isObservedIn
Indicates that something (such as a phenomenon, property, or behavior) is detected, recorded, or found to occur within a particular context, setting, or environment.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c3cf748190987838029d9f7fff |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.