Triple
T23010239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eburones |
E572884
|
entity |
| Predicate | ethnonymStatus |
P150643
|
FINISHED |
| Object | disappeared after Roman conquest |
—
|
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: disappeared after Roman conquest | Statement: [Eburones, ethnonymStatus, disappeared after Roman conquest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnonymStatus Context triple: [Eburones, ethnonymStatus, disappeared after Roman conquest]
-
A.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
-
B.
ethnonymInLanguage
Indicates that a given term is the name used in a specified language to refer to the people of a particular ethnic group or nationality.
-
C.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
D.
isEthnonymic
Indicates that something (typically a name or term) is derived from or based on the name of an ethnic group or people.
-
E.
ethnonymScope
Indicates the scope or range of people, groups, or contexts to which a given ethnonym (name of an ethnic group) applies.
- F. None of above. chosen
Provenance (4 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18359f5548190b15a139eb09e30a0 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:51 p.m.