Triple
T30943338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fragile Express |
E788319
|
entity |
| Predicate | competitorInFiction |
P103334
|
FINISHED |
| Object | Bridges |
—
|
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: Bridges | Statement: [Fragile Express, competitorInFiction, Bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitorInFiction Context triple: [Fragile Express, competitorInFiction, Bridges]
-
A.
fictionalRivalOf
chosen
Indicates a rivalry relationship that exists between two entities only within a fictional or narrative context.
-
B.
fictionalCompetitorType
Indicates that one fictional entity is characterized as a competitor of a specified type relative to another fictional entity or context.
-
C.
fictionalCounterpartIn
Indicates that one entity serves as a fictional analogue or stand-in for another entity within a specified work or fictional universe.
-
D.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
E.
composedByFictionalCharacter
Indicates that a work or piece of content is (within the narrative) created or authored by a fictional character.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 8:53 p.m.