Triple
T35960255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veromandui |
E1039974
|
entity |
| Predicate | romanCivitasCapitalPresentDay |
P184477
|
FINISHED |
| Object | Saint-Quentin |
—
|
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: Saint-Quentin | Statement: [Veromandui, romanCivitasCapitalPresentDay, Saint-Quentin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanCivitasCapitalPresentDay Context triple: [Veromandui, romanCivitasCapitalPresentDay, Saint-Quentin]
-
A.
romanCivitasCapital
chosen
Indicates that a given settlement serves as the principal town or administrative center (capital) of a specified Roman civitas (local community or district).
-
B.
romanCivitasName
Indicates that an entity bears the official Roman civitas (city or community) name associated with it.
-
C.
romanProvinceCapital
Indicates that one place served as the administrative capital of a specified Roman province.
-
D.
romanTownLocatedIn
Indicates that a Roman town is geographically situated within a specified larger area, such as a region, province, or territory.
-
E.
ancientCapitalLocatedIn
Indicates that a city served as the capital of an ancient polity or civilization and was geographically situated within a specified region or territory.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.