Triple
T16585135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Sors |
E402936
|
entity |
| Predicate | centuryOfFictionalActivity |
P18945
|
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: [Ivan Sors, centuryOfFictionalActivity, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centuryOfFictionalActivity Context triple: [Ivan Sors, centuryOfFictionalActivity, 20th century]
-
A.
fictionalCenturyOfOrigin
Indicates the fictional century in which an entity is depicted as having originated or first appeared within its narrative world.
-
B.
fictionalEra
chosen
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
C.
fictionalAge
Indicates the age attributed to an entity within a fictional or narrative context, rather than its real-world age.
-
D.
activeInFictionalYear
Indicates that an entity is active or operating during a specified fictional or imaginary year within a narrative or fictional timeline.
-
E.
activityEndCentury
Indicates the century during which an activity or ongoing action came to an end.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599b057881909fcb8bbb156633a8 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.