Triple
T35019359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aníbal de Souza |
E1010150
|
entity |
| Predicate | decadeOfFictionalEvents |
P97955
|
FINISHED |
| Object | 1940s |
—
|
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: 1940s | Statement: [Aníbal de Souza, decadeOfFictionalEvents, 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decadeOfFictionalEvents Context triple: [Aníbal de Souza, decadeOfFictionalEvents, 1940s]
-
A.
approximateFictionalEra
Indicates that one entity specifies an estimated or loosely defined fictional time period in which another entity is set or takes place.
-
B.
fictionalEra
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
C.
endsInFictionalYear
Indicates that an event, story, or timeline concludes in a year that exists only within a fictional or imagined setting.
-
D.
launchedInFictionalYear
Indicates that an entity is depicted as being launched in a specified fictional or imaginary year within a narrative or fictional universe.
-
E.
heldInDecade
chosen
Indicates that an event or activity took place during a specific decade.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.