Triple
T20021100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna |
E494857
|
entity |
| Predicate | hasAgencyInPlot |
P138397
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Vienna, hasAgencyInPlot, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgencyInPlot Context triple: [Vienna, hasAgencyInPlot, yes]
-
A.
hasFBIAsOrganizationInPlot
Indicates that the FBI appears as an organization involved in the narrative or storyline of the work.
-
B.
hasMissionAgency
Indicates that an entity is associated with, overseen by, or carried out under the responsibility of a particular mission agency.
-
C.
hasAgent
Indicates that an action or event is carried out or initiated by a particular agent.
-
D.
belongsToAgency
Indicates that an entity is under the authority, control, or affiliation of a specific agency.
-
E.
allegedAgentOf
Indicates that one entity is claimed or suspected, but not confirmed, to be the agent responsible for an action or event involving 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623fe1988190a1c09d392d866dc8 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:35 p.m.