Triple
T19776960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrondissement of Soissons |
E475026
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Vic-sur-Aisne |
—
|
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: Vic-sur-Aisne | Statement: [Arrondissement of Soissons, contains, Vic-sur-Aisne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vic-sur-Aisne Context triple: [Arrondissement of Soissons, contains, Vic-sur-Aisne]
-
A.
Vic-sur-Aisne
chosen
Vic-sur-Aisne is a commune in the Aisne department of northern France, known for its riverside setting and historic architecture.
-
B.
Vailly-sur-Aisne
Vailly-sur-Aisne is a commune in northern France’s Aisne department, known for its World War I history and location along the Aisne River.
-
C.
Neufchâtel-sur-Aisne
Neufchâtel-sur-Aisne is a small commune in northern France situated along the Aisne River.
-
D.
Villers-le-Peuplier
Villers-le-Peuplier is a village in the municipality of Hannut in the province of Liège, Belgium.
-
E.
Triel-sur-Seine
Triel-sur-Seine is a commune in the Yvelines department of north-central France, situated along the Seine River to the northwest of Paris.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65360cca08190957c36b1a440542c |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:48 p.m.