Triple
T25313354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lingones |
E634664
|
entity |
| Predicate | militaryStatusUnderRome |
P60438
|
FINISHED |
| Object | allied to Rome |
—
|
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: allied to Rome | Statement: [Lingones, militaryStatusUnderRome, allied to Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryStatusUnderRome Context triple: [Lingones, militaryStatusUnderRome, allied to Rome]
-
A.
militaryContributionToRome
chosen
Indicates that an entity provides military forces, support, or resources in service of or on behalf of Rome.
-
B.
wasRomanMilitaryZoneSince
Indicates that a place or region has been designated and used as a Roman military zone starting from a specified point in time.
-
C.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
-
D.
politicalStatusInAntiquity
Indicates the political condition or classification an entity held during ancient times, such as its form of governance, sovereignty, or dependency.
-
E.
roleInRomanPeriod
Indicates that an entity held a specific role, function, or status during the Roman period.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:27 p.m.