Triple
T37105308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4179 Toutatis |
E918823
|
entity |
| Predicate | radarImagingRevealed |
P187477
|
FINISHED |
| Object | bilobate shape |
—
|
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: bilobate shape | Statement: [4179 Toutatis, radarImagingRevealed, bilobate shape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radarImagingRevealed Context triple: [4179 Toutatis, radarImagingRevealed, bilobate shape]
-
A.
radarInterface
Indicates that one entity serves as or provides a radar-based interface or interaction layer for another entity.
-
B.
radarFunction
Indicates that one entity serves as the functional role, purpose, or operational capability of a radar system in relation to another entity.
-
C.
radarModel
Indicates that one entity is a radar system and the other is the specific model or type designation of that radar.
-
D.
radarEquipment
Indicates that one entity is radar equipment used for detecting, tracking, or measuring objects relative to another entity.
-
E.
radarType
Indicates the specific category or classification of radar associated with an entity.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:14 p.m.