Triple
T32231449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civitas Tungrorum |
E823350
|
entity |
| Predicate | hadCityWall |
P164891
|
FINISHED |
| Object | Tongeren |
—
|
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: Tongeren | Statement: [Civitas Tungrorum, hadCityWall, Tongeren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCityWall Context triple: [Civitas Tungrorum, hadCityWall, Tongeren]
-
A.
hadCityWalls
chosen
Indicates that a city or settlement possessed defensive walls surrounding it.
-
B.
hasCityWallsFrom
Indicates that a city’s defensive walls originate from, or were constructed starting at, a specified source location or structure.
-
C.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
D.
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.
-
E.
hasCityWallsFromPeriod
Indicates that a city possesses defensive walls that date from a specified historical period.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbfbd660819087be1af4b275cfcb |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:39 a.m.