Triple
T1324687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ligurians |
E28298
|
entity |
| Predicate | ethnogenesisInfluenceOn |
P21716
|
FINISHED |
| Object | modern Ligurians |
—
|
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: modern Ligurians | Statement: [Ligurians, ethnogenesisInfluenceOn, modern Ligurians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnogenesisInfluenceOn Context triple: [Ligurians, ethnogenesisInfluenceOn, modern Ligurians]
-
A.
ethnogenesisRegion
Indicates the geographic region where the formation or emergence of an ethnic group took place.
-
B.
hasHistoricalInfluenceFrom
Indicates that one entity’s characteristics, development, or significance have been shaped or affected by the past actions, ideas, or legacy of another entity.
-
C.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
D.
affectedEthnicGroup
Indicates that a particular ethnic group is impacted or influenced by an event, condition, policy, or action.
-
E.
influencedFormationOf
chosen
Indicates that one entity played a significant role in shaping, initiating, or contributing to the development or establishment of another entity.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19e81c0819092f85201ae34422a |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.