Triple
T29103576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigurini |
E736701
|
entity |
| Predicate | timeOfRomanIncorporation |
P126247
|
FINISHED |
| Object | 1st century BC |
—
|
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: 1st century BC | Statement: [Tigurini, timeOfRomanIncorporation, 1st century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfRomanIncorporation Context triple: [Tigurini, timeOfRomanIncorporation, 1st century BC]
-
A.
eraOfRomanConquest
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
-
B.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
-
C.
approximateRomanConquestCentury
chosen
Indicates the approximate century in which the Romans conquered or gained control over a given entity.
-
D.
underRomanRuleBecame
Indicates that an entity, once under Roman political or administrative control, subsequently transformed into or was reconstituted as another specified entity.
-
E.
becameRomanColony
Indicates that a place or community transitioned into the formal status of a Roman colony under Roman authority.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 11:14 a.m.