Triple
T17910573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homeworld Gems |
E447807
|
entity |
| Predicate | viewsEarthAs |
P18771
|
FINISHED |
| Object | colony |
—
|
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: colony | Statement: [Homeworld Gems, viewsEarthAs, colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsEarthAs Context triple: [Homeworld Gems, viewsEarthAs, colony]
-
A.
viewedEarthAs
chosen
Indicates perceiving or regarding Earth in a particular way, often reflecting an attitude, interpretation, or conceptual perspective toward the planet.
-
B.
forEarthApprox
Indicates an approximate or estimated value or condition as it pertains to Earth or an Earth-related context.
-
C.
capitalPlanet
Indicates that one planet serves as the capital world or primary governing center for another entity (such as a political or administrative body).
-
D.
visibleFromSpace
Indicates that something can be seen or detected from outer space, typically by astronauts or satellites in orbit around a celestial body.
-
E.
viewOnMoon
Indicates that an entity has a visual perspective or observable view from the surface or vicinity of the 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49ea017d081908be850a39edf601f |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.