Triple
T29186137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmund Gundersen |
E739873
|
entity |
| Predicate | pastRoleOnPlanet |
P166410
|
FINISHED |
| Object | colonial overseer |
—
|
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: colonial overseer | Statement: [Edmund Gundersen, pastRoleOnPlanet, colonial overseer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pastRoleOnPlanet Context triple: [Edmund Gundersen, pastRoleOnPlanet, colonial overseer]
-
A.
roleAtThePlanet
Indicates that an entity holds or performs a specific role or function at, on, or for a particular planet.
-
B.
notablePlanetRole
Indicates that a planet holds a significant or distinguished role or function within a particular context or system.
-
C.
economicRolePast
Indicates that an entity previously held a specific economic function, position, or role in the past.
-
D.
mayHavePriorRole
Indicates that an entity is allowed or expected to have held a specified role at some earlier time.
-
E.
roleAtPluto
Indicates that an entity holds or held a specific role or position within the organization or project named Pluto.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6638722fc819098f18314dfa88a6c |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 11:59 a.m.