Triple
T32280213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American (wizarding world) |
E824668
|
entity |
| Predicate | hasCapitalMagicalCity |
P198171
|
FINISHED |
| Object | New York City (wizarding world) |
—
|
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: New York City (wizarding world) | Statement: [American (wizarding world), hasCapitalMagicalCity, New York City (wizarding world)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalMagicalCity Context triple: [American (wizarding world), hasCapitalMagicalCity, New York City (wizarding world)]
-
A.
portCityOfRealm
Indicates that a city serves as a primary seaport or harbor for a particular realm, such as a country, kingdom, or region.
-
B.
containsCapitalCity
Indicates that a geographic or political region includes within its boundaries the capital city associated with it.
-
C.
cityOfFictionalLocation
Indicates that a fictional location is situated within or associated with a particular city.
-
D.
hasFamousCity
Indicates that an entity possesses or is associated with a city that is widely recognized or renowned.
-
E.
capitalOfHisKingdom
Indicates that one entity serves as the capital city of the kingdom ruled or possessed by 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
| PDg | Predicate description generation | batch_69feced436a48190b761db7df2d6b6bd |
completed | May 9, 2026, 6:06 a.m. |
Created at: May 1, 2026, 12:43 a.m.