Triple
T10320124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raetic people |
E242115
|
entity |
| Predicate | possibleOriginTheory |
P57097
|
FINISHED |
| Object | related to Etruscans |
—
|
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: related to Etruscans | Statement: [Raetic people, possibleOriginTheory, related to Etruscans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleOriginTheory Context triple: [Raetic people, possibleOriginTheory, related to Etruscans]
-
A.
originBelief
chosen
Indicates a belief or assumption about where something or someone comes from or originated.
-
B.
confirmedTheoryOf
Indicates that one entity is recognized or established as the validated theoretical explanation or model of another entity.
-
C.
originMyth
Indicates the traditional myth or legendary narrative that explains the beginnings or creation of a people, place, institution, or phenomenon.
-
D.
allegedPhenomenon
Indicates that something is claimed or reported to be a phenomenon, but its existence, cause, or nature is uncertain or disputed.
-
E.
hasUncertainOrigin
Indicates that the origin or source of an entity, event, or information is unknown, unclear, or not reliably established.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:50 a.m.