Triple
T29188033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castilon |
E739922
|
entity |
| Predicate | notableLocationOnPlanet |
P3858
|
FINISHED |
| Object | Colossus platform |
E1854314
|
NE 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: Colossus platform | Statement: [Castilon, notableLocationOnPlanet, Colossus platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLocationOnPlanet Context triple: [Castilon, notableLocationOnPlanet, Colossus platform]
-
A.
notableLocationOnHomeworld
Indicates that a specific location is notable or significant on the entity’s homeworld.
-
B.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
C.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
D.
notableLocation
chosen
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
E.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
- F. None of above.
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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a031045669c8190944781a48d09b5b6 |
completed | May 12, 2026, 11:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a267e939ee88190bb3572a603b5571d |
completed | June 8, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_6a030fa775848190839b388f950d0364 |
completed | May 12, 2026, 11:31 a.m. |
Created at: April 28, 2026, noon