Triple
T28899433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mad Gear gang |
E732912
|
entity |
| Predicate | fictionalHomeCity |
P107735
|
FINISHED |
| Object | Metro City |
—
|
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: Metro City | Statement: [Mad Gear gang, fictionalHomeCity, Metro City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalHomeCity Context triple: [Mad Gear gang, fictionalHomeCity, Metro City]
-
A.
cityOfFictionalResidence
chosen
Indicates that a fictional character or entity resides in, or is associated with living in, a particular city within a narrative or fictional context.
-
B.
cityOfFictionalOrigin
Indicates the city from which a fictional character, entity, or work is described as originating within its narrative or fictional universe.
-
C.
partOfFictionalCity
Indicates that one entity is a component, area, or subdivision within a larger fictional city.
-
D.
fictionalBirthPlace
Indicates the fictional location where a character or entity is described as having been born within a narrative or imagined context.
-
E.
townOfFictionalSetting
Indicates that a town serves as the fictional setting or primary location where the events of a narrative work take place.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 28, 2026, 8:01 a.m.