Triple
T4626848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shobogan |
E101117
|
entity |
| Predicate | cultureComparedToTimeLords |
P57517
|
FINISHED |
| Object | more rustic |
—
|
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: more rustic | Statement: [Shobogan, cultureComparedToTimeLords, more rustic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultureComparedToTimeLords Context triple: [Shobogan, cultureComparedToTimeLords, more rustic]
-
A.
perceptionOnGallifrey
Indicates a perception, observation, or sensory experience that occurs specifically within the context or location of Gallifrey.
-
B.
impactOnTimeLords
Indicates the effect or consequence that something has on Time Lords, particularly how it influences their state, behavior, or circumstances.
-
C.
timeLordSocietyStatus
Indicates the social rank or standing an individual holds within Time Lord society.
-
D.
followsInCanon
Indicates that one entity occurs later than and in continuity with another within an established narrative or canonical sequence.
-
E.
inUniverseAge
Indicates the age of an entity as measured within the timeline or continuity of a specific fictional or defined universe.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a0a7b588190bc6552ee5babb198 |
completed | March 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:13 p.m.