Triple
T17359459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 25143 Itokawa |
E422028
|
entity |
| Predicate | hasContactBinaryMorphology |
P127194
|
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: [25143 Itokawa, hasContactBinaryMorphology, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactBinaryMorphology Context triple: [25143 Itokawa, hasContactBinaryMorphology, yes]
-
A.
hasContactVariety
Indicates that one entity is associated with a specific type or variety of contact information or communication channel.
-
B.
hasBinary
Indicates that one entity is associated with another entity in a binary (two-component) relationship, typically as one of the two members of a pair.
-
C.
hasMorphologicalType
Indicates that an entity possesses or is classified by a particular morphological type or structural form.
-
D.
hasContactType
Indicates the specific kind or category of contact relationship that exists between two entities.
-
E.
hasSurfaceConnections
Indicates that one entity is linked to another through connections or interfaces that occur at or across their surfaces.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4be7448190988593ee342348c1 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.