Triple
T23160799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suessiones |
E578574
|
entity |
| Predicate | modernCityDerivesNameFrom |
P26180
|
FINISHED |
| Object | Soissons |
—
|
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: Soissons | Statement: [Suessiones, modernCityDerivesNameFrom, Soissons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCityDerivesNameFrom Context triple: [Suessiones, modernCityDerivesNameFrom, Soissons]
-
A.
cityNamedAfter
chosen
Indicates that one city derives its name from or was named in honor of another entity, such as a person, place, or concept.
-
B.
cityDerivation
Indicates that one city is derived from, created out of, or established as a successor to another city.
-
C.
majorCityFounded
Indicates that one entity is a major city and the other is the date or event of its founding.
-
D.
developedAsCityDueTo
Indicates that a settlement or area became a city specifically as a result of the influence, presence, or development of the referenced cause or factor.
-
E.
modernNameOfServedSettlement
Indicates that the object is the current, modern name of the settlement that is or was served by the subject (e.g., a facility, infrastructure, or service).
- F. None of above.
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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f006930819097aafef87405d737 |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:02 p.m.