Triple
T23954124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomainia |
E603731
|
entity |
| Predicate | alliedWithParodies |
P154490
|
FINISHED |
| Object | Fascist Italy |
—
|
NE NERFINISHED |
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: Fascist Italy | Statement: [Tomainia, alliedWithParodies, Fascist Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedWithParodies Context triple: [Tomainia, alliedWithParodies, Fascist Italy]
-
A.
alliesInFiction
Indicates that two or more entities are portrayed as allies or cooperative partners within a fictional context or narrative.
-
B.
alliedWithInFilm
Indicates that two characters or entities are portrayed as allies or cooperating on the same side within the context of a specific film.
-
C.
alliedWithBasedOn
Indicates a relationship where two or more entities are allied with each other specifically due to, or grounded in, a particular basis, condition, or shared factor.
-
D.
oftenAlliedWith
Indicates that one entity is frequently or habitually allied or aligned in cooperation with another entity.
-
E.
alliesOf
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d558748190a51b5732a3e6713c |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:21 p.m.