Triple
T16523725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusitania |
E401382
|
entity |
| Predicate | preRomanLanguages |
P88155
|
FINISHED |
| Object | Lusitanian language |
—
|
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: Lusitanian language | Statement: [Lusitania, preRomanLanguages, Lusitanian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preRomanLanguages Context triple: [Lusitania, preRomanLanguages, Lusitanian language]
-
A.
preRomanLanguage
chosen
Indicates that a language existed or was used in a region before the arrival or dominance of Roman rule or the Latin language.
-
B.
preRomanName
Indicates the name by which an entity (such as a place or people) was known before the Roman period or prior to receiving a Roman-era name.
-
C.
preRomanPolity
Indicates that an entity functioned as a political or governmental unit that existed before the establishment or dominance of Roman rule in a given region.
-
D.
preRomanRegion
Indicates that a region existed or was defined in the period before Roman rule or influence.
-
E.
preRomanContext
Indicates that something exists, occurs, or is situated in a historical or cultural context prior to 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed2622c8190b6429a49ca92284a |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.