Triple
T16654051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | António Mora |
E404678
|
entity |
| Predicate | fictionalExistence |
P14491
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [António Mora, fictionalExistence, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalExistence Context triple: [António Mora, fictionalExistence, 20th century]
-
A.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
B.
fictionalStatus
chosen
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
-
C.
fictionalFocus
Indicates that the primary emphasis or attention within a context is placed on fictional content, elements, or aspects.
-
D.
fictionalSon
Indicates that one entity is portrayed as the son of another entity within a fictional or narrative context.
-
E.
fictionalUse
Indicates that one entity makes use of another within a fictional or imaginary context, rather than in real-world usage.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf92de48190aaae3e93039b17f3 |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.