Triple
T37172559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telavåg |
E920952
|
entity |
| Predicate | hasPostwarStatus |
P200106
|
FINISHED |
| Object | inhabited village |
—
|
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: inhabited village | Statement: [Telavåg, hasPostwarStatus, inhabited village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostwarStatus Context triple: [Telavåg, hasPostwarStatus, inhabited village]
-
A.
statusPostWar
chosen
Indicates the condition or situation of an entity after a war has ended.
-
B.
hasPostwarConcentration
Indicates that an entity exhibits a notable focus, activity, or significance during the postwar period.
-
C.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
D.
hasPostWarIssues
Indicates that an entity experiences problems, challenges, or complications that arise in the period following a war or major conflict.
-
E.
hasPostwarArchitecture
Indicates that an entity possesses architectural features or structures that were designed or built in the period following a major war, typically reflecting postwar styles or reconstruction efforts.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.