Triple
T30580737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Small Axe: Mangrove |
E778373
|
entity |
| Predicate | timeInUniverseStarts |
P45888
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Small Axe: Mangrove, timeInUniverseStarts, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInUniverseStarts Context triple: [Small Axe: Mangrove, timeInUniverseStarts, 1968]
-
A.
inUniverseAge
Indicates the age of an entity as measured within the timeline or continuity of a specific fictional or defined universe.
-
B.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
C.
inUniverseDate
chosen
Indicates that an entity is associated with or occurs on a specific date within a fictional or defined universe’s internal timeline.
-
D.
setInUniverseDuring
Indicates that an event, story, or situation takes place within a particular universe during a specified time or period.
-
E.
universeNumber
Indicates that an entity is associated with a specific universe identified by a particular number or index.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6894176d0819096fe66b9baab66f1 |
completed | May 2, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:23 p.m.