Triple
T36411634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watch of Messina |
E896894
|
entity |
| Predicate | isLocatedInFictional |
P98600
|
FINISHED |
| Object | Messina |
—
|
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: Messina | Statement: [Watch of Messina, isLocatedInFictional, Messina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInFictional Context triple: [Watch of Messina, isLocatedInFictional, Messina]
-
A.
locatedInFictionalContext
chosen
Indicates that one entity exists or occurs within the setting or universe of a fictional work associated with another entity.
-
B.
residesInFictionalLocation
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
C.
locatedInFictionalCountry
Indicates that an entity exists or is situated within a country that is fictional rather than real.
-
D.
basedInFictionalSetting
Indicates that an entity’s primary location or setting exists within a fictional or imaginary world rather than the real world.
-
E.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:10 p.m.