Triple
T14269437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ager Gallicus |
E353738
|
entity |
| Predicate | romanLegalStatus |
P40055
|
FINISHED |
| Object | ager publicus |
—
|
LITERAL FINISHED |
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: ager publicus | Statement: [Ager Gallicus, romanLegalStatus, ager publicus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanLegalStatus Context triple: [Ager Gallicus, romanLegalStatus, ager publicus]
-
A.
usedLegalStatus
Indicates that one entity applies or relies on the legal status or classification of another entity in a given context.
-
B.
civicStatus
Indicates the legal or social standing of an individual within a civic or societal framework, such as marital or citizenship status.
-
C.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
D.
legalCodeStatus
Indicates the legal or regulatory status assigned to a specific code within a legal or statutory system (e.g., active, repealed, pending).
-
E.
legalStatusInEmpire
chosen
Indicates the formal legal standing or classification an entity holds within a particular empire’s legal and administrative system.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de657fe6708190b41de48c43cff647 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.