Triple
T20682556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wokolo |
E508330
|
entity |
| Predicate | relativeSizeOnUmbriel |
P62442
|
FINISHED |
| Object | largestKnown |
—
|
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: largestKnown | Statement: [Wokolo, relativeSizeOnUmbriel, largestKnown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSizeOnUmbriel Context triple: [Wokolo, relativeSizeOnUmbriel, largestKnown]
-
A.
relativeSizeInSaturnSystem
Indicates the comparative size relationship of an object relative to other objects within the Saturn system.
-
B.
relativeSizeToPluto
Indicates how the size of one entity compares to the size of Pluto.
-
C.
relativeSizeInUranianSystem
chosen
Indicates the comparative size relationship between two objects within the Uranian system (e.g., Uranus, its rings, or its moons).
-
D.
relativeSizeOnTethys
Indicates how the size of one entity compares to another specifically in the context of Tethys.
-
E.
isOnLargerMoonOf
Indicates that one entity is located on a moon that is larger than another referenced moon.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea9771881908a077d01f53f6d52 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:45 a.m.