Triple
T27941520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resources Development Administration |
E700761
|
entity |
| Predicate | homePlanetOfOrganization |
P52572
|
FINISHED |
| Object | Earth |
—
|
NE NERFINISHED |
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: Earth | Statement: [Resources Development Administration, homePlanetOfOrganization, Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homePlanetOfOrganization Context triple: [Resources Development Administration, homePlanetOfOrganization, Earth]
-
A.
homePlanet
Indicates the planet that serves as the native or original world of an entity.
-
B.
homePlanetSystem
Indicates that one entity is the planetary system that serves as the home or origin system of the other entity.
-
C.
homeCompany
Indicates that one entity serves as the primary or base company associated with another entity, such as a person or subsidiary.
-
D.
mainOffice
Indicates that one location or office serves as the primary or central office for an organization or entity.
-
E.
hostPlanet
chosen
Indicates that one entity serves as the primary planetary body on which the other entity resides, originates, or is based.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:18 p.m.