Triple
T29084640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Arar |
E734071
|
entity |
| Predicate | HelvetiiStatus |
P165986
|
FINISHED |
| Object | migrating population |
—
|
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: migrating population | Statement: [Battle of the Arar, HelvetiiStatus, migrating population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HelvetiiStatus Context triple: [Battle of the Arar, HelvetiiStatus, migrating population]
-
A.
HethIs
Indicates that one entity is identified as or equated with another entity, expressing a basic “is” or “being” relationship between them.
-
B.
припадаДржавиПоВрху
Indicates that something belongs to or is under the sovereignty of a state based on its summit or highest point.
-
C.
landerStatus
Indicates the current operational or situational state of a lander in its mission lifecycle.
-
D.
NorbulingkaStatus
Indicates the current condition, designation, or preservation state associated with Norbulingka.
-
E.
humanSettlementStatus
Indicates the classification of a place in terms of its status as a human settlement (e.g., whether and how it is recognized or designated as a populated place).
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6614638d481909dd167f9c8c7055c |
completed | May 2, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 10:59 a.m.