Triple
T36126922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Underdog |
E1044905
|
entity |
| Predicate | settingCityType |
P142042
|
FINISHED |
| Object | suburban Sydney |
—
|
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: suburban Sydney | Statement: [The Underdog, settingCityType, suburban Sydney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingCityType Context triple: [The Underdog, settingCityType, suburban Sydney]
-
A.
settingCity
Indicates that a work or event takes place in, or is primarily located within, a particular city.
-
B.
cityTypeLocation
chosen
Indicates that a location is classified as a specific type of city (e.g., capital, metropolitan, coastal).
-
C.
cityGroupType
Indicates the classification or category type assigned to a group of cities within a larger organizational or geographic structure.
-
D.
seeCityType
Indicates that an entity observes or recognizes the classification or type of a city (e.g., metropolitan, rural, coastal).
-
E.
connectsTypeOfCity
Indicates a relationship where one entity is linked to another as a specific type or category of city.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:08 p.m.