Triple
T4822498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irma la Douce |
E107741
|
entity |
| Predicate | setIn |
P1393
|
FINISHED |
| Object | 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: Paris | Statement: [Irma la Douce, setIn, Paris]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paris Context triple: [Irma la Douce, setIn, Paris]
-
A.
Paris
chosen
Paris is the capital and largest city of France, renowned for its historic architecture, art, fashion, and cultural influence worldwide.
-
B.
Paris
Paris is a prince of Troy in Greek mythology, best known for judging the beauty contest of the goddesses and for abducting Helen, which sparked the Trojan War.
-
C.
Parigi
Parigi is a coastal town that serves as the administrative center of Parigi Moutong Regency in Central Sulawesi, Indonesia.
-
D.
Lyon
Lyon is a major city in east-central France known for its historical and architectural landmarks, gastronomy, and role as a key economic and cultural center.
-
E.
Paris Bar
The Paris Bar is the professional association and regulatory body for lawyers practicing in Paris, France.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6caa95ec8190bea525dbf3a00477 |
completed | March 20, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be4dae0008819089c54a3815e578bc |
completed | March 21, 2026, 7:50 a.m. |
Created at: March 20, 2026, 1:24 p.m.