Triple
T7700979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Paris (1814) |
E174492
|
entity |
| Predicate | signedIn |
P441
|
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: [Treaty of Paris (1814), signedIn, Paris]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paris Context triple: [Treaty of Paris (1814), signedIn, Paris]
-
A.
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.
-
B.
Paris
chosen
Paris is the capital and largest city of France, renowned for its historic architecture, art, fashion, and cultural influence worldwide.
-
C.
Paris
Paris is a major Chilean department store and retail chain offering a wide range of apparel, home goods, and consumer products.
-
D.
Paris
Paris is a budget-oriented AMD Sempron processor core designed for entry-level desktop computing.
-
E.
Parigi
Parigi is a coastal town that serves as the administrative center of Parigi Moutong Regency in Central Sulawesi, Indonesia.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70288d02c819093d6f0e47707d0a3 |
completed | March 27, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8d6ab0ab48190b273d07db6d74c33 |
completed | March 29, 2026, 7:37 a.m. |
Created at: March 27, 2026, 4:03 p.m.