Triple
T534623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Europeans |
E12298
|
entity |
| Predicate | gaveRiseTo |
P1257
|
FINISHED |
| Object | Germanic peoples |
—
|
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: Germanic peoples | Statement: [Indo-Europeans, gaveRiseTo, Germanic peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaveRiseTo Context triple: [Indo-Europeans, gaveRiseTo, Germanic peoples]
-
A.
emergedFrom
chosen
Indicates that one entity originated, arose, or came forth from another entity or source.
-
B.
foundedAsResultOf
Indicates that one entity was established or created as a direct consequence or outcome of another event, action, or circumstance.
-
C.
became
Indicates a change of state or status in which one entity transitions into or assumes the role, condition, or identity of another.
-
D.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with another entity.
-
E.
revivedBy
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.