Triple
T30162789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tungri |
E766712
|
entity |
| Predicate | romanCivitas |
P135302
|
FINISHED |
| Object | Civitas Tungrorum |
—
|
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: Civitas Tungrorum | Statement: [Tungri, romanCivitas, Civitas Tungrorum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanCivitas Context triple: [Tungri, romanCivitas, Civitas Tungrorum]
-
A.
romanCivitasName
chosen
Indicates that an entity bears the official Roman civitas (city or community) name associated with it.
-
B.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
C.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
D.
RomanTribe
Indicates a relationship where an entity belongs to, is classified within, or is associated with a specific Roman tribe.
-
E.
romanProvinceCapital
Indicates that one place served as the administrative capital of a specified Roman province.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 7:22 p.m.