Triple
T32231448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civitas Tungrorum |
E823350
|
entity |
| Predicate | hadForum |
P3479
|
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, hadForum, Tongeren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadForum Context triple: [Civitas Tungrorum, hadForum, Tongeren]
-
A.
forum
Indicates that an entity hosts or is associated with an online discussion space where users can post messages and interact.
-
B.
hasAdditionalForum
Indicates that an entity is associated with one or more supplementary or secondary discussion forums beyond its primary forum.
-
C.
hadURL
Indicates that an entity was associated with or linked to a specific URL at some point in time.
-
D.
hadFort
chosen
Indicates that an entity possessed, controlled, or contained a fort at some time.
-
E.
providesForumFor
Indicates that one entity offers a setting, platform, or opportunity in which another entity can be discussed, expressed, or interact.
- 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.