Triple
T17293491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senlis |
E419845
|
entity |
| Predicate | hasCityWallsFrom |
P126852
|
FINISHED |
| Object | Gallo-Roman period |
—
|
LITERAL 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: Gallo-Roman period | Statement: [Senlis, hasCityWallsFrom, Gallo-Roman period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityWallsFrom Context triple: [Senlis, hasCityWallsFrom, Gallo-Roman period]
-
A.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
B.
hasCityWallFunction
Indicates that an entity serves the functional role of a city wall, such as providing defense, enclosure, or boundary protection for an urban area.
-
C.
hasCityWallGates
Indicates that a city wall includes one or more gates that provide passage through it.
-
D.
hasHistoricTownWallsRemnants
Indicates that remnants of historic town walls are present and associated with the subject entity.
-
E.
hasPeaceWalls
Indicates that there exist physical barriers or walls separating groups or areas to reduce or prevent conflict or violence between them.
- F. None of above. chosen
Provenance (4 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43785383881908ec61ddf5e2193cf |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:40 a.m.