Triple
T29103357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavay |
E736695
|
entity |
| Predicate | hasPreservedMonument |
P199461
|
FINISHED |
| Object | Roman forum of Bagacum |
—
|
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: Roman forum of Bagacum | Statement: [Bavay, hasPreservedMonument, Roman forum of Bagacum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreservedMonument Context triple: [Bavay, hasPreservedMonument, Roman forum of Bagacum]
-
A.
hasWorkOnMonument
Indicates that an entity has created, contributed to, or performed work on a particular monument.
-
B.
hasScheduledMonument
Indicates that an entity is associated with, or contains, a site or structure officially designated as a scheduled monument.
-
C.
hasPrimaryMonument
Indicates that an entity is associated with its main or most significant monument.
-
D.
hasNumberOfMonuments
Indicates the specific count of monuments associated with or present in a given entity.
-
E.
hasMonumentAt
Indicates that a monument is located at or associated with a specific place or site.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
| PDg | Predicate description generation | batch_69ff3b323a748190827165f1cb274141 |
completed | May 9, 2026, 1:48 p.m. |
Created at: April 28, 2026, 11:13 a.m.