Triple
T7852158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirta |
E182081
|
entity |
| Predicate | formerInhabitantsEvacuated |
P67099
|
FINISHED |
| Object | 1930 |
—
|
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: 1930 | Statement: [Hirta, formerInhabitantsEvacuated, 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerInhabitantsEvacuated Context triple: [Hirta, formerInhabitantsEvacuated, 1930]
-
A.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
B.
permanentlyEvacuated
chosen
Indicates that an entity has been removed from a place or situation with no intention or expectation of returning.
-
C.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
-
D.
evacuatedCity
Indicates that people or populations were removed from or left a city, typically due to danger or emergency conditions.
-
E.
evacuatedUnit
Indicates that a unit has been removed from a location or situation, typically for safety or strategic reasons.
- 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_69ca82869ee08190b8f9040dbc2c0467 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb18ec48548190960bd564a60effa8 |
completed | March 31, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:51 p.m.