Triple
T17070581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accor Arena |
E414206
|
entity |
| Predicate | ownedBy |
P347
|
FINISHED |
| Object | City of Paris |
E568
|
NE 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: City of Paris | Statement: [Accor Arena, ownedBy, City of Paris]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Paris Context triple: [Accor Arena, ownedBy, City of Paris]
-
A.
Ville de Paris
Ville de Paris was a prominent French ship of the line, originally the flagship of Admiral de Grasse, that played a central role in major naval engagements during the American Revolutionary War.
-
B.
Parigi
Parigi is a town located in the Vikarabad district of the Indian state of Telangana.
-
C.
Parigi
Parigi is a coastal town that serves as the administrative center of Parigi Moutong Regency in Central Sulawesi, Indonesia.
-
D.
Paris
Paris is a budget-oriented AMD Sempron processor core designed for entry-level desktop computing.
-
E.
Paris
chosen
Paris is the capital and largest city of France, renowned for its historic architecture, art, fashion, and cultural influence worldwide.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc0982c8190916f9905ddb5e575 |
completed | April 18, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a014823d0a8819095491aef9b258971 |
completed | May 11, 2026, 3:08 a.m. |
Created at: April 10, 2026, 5:34 a.m.