Triple
T30987045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Taylor |
E789555
|
entity |
| Predicate | worldEncountered |
P193665
|
FINISHED |
| Object | planet ruled by intelligent apes |
—
|
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: planet ruled by intelligent apes | Statement: [George Taylor, worldEncountered, planet ruled by intelligent apes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldEncountered Context triple: [George Taylor, worldEncountered, planet ruled by intelligent apes]
-
A.
worldName
Indicates that an entity has or is associated with a specific world’s name.
-
B.
worldType
Indicates the classification or category of world or environment that an entity is associated with.
-
C.
worldNumber
Indicates the specific world, dimension, or universe identifier associated with an entity or event.
-
D.
worldFirst
Indicates that an entity is the first in the world to achieve, create, or perform a particular thing or action.
-
E.
worldParallels
Indicates that one world, scenario, or context runs in parallel to another, sharing similar structures, events, or conditions without being identical.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: April 29, 2026, 8:56 p.m.