Triple
T37172510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telavåg |
E920951
|
entity |
| Predicate | hasRebuiltStatus |
P64256
|
FINISHED |
| Object | rebuilt after World War II destruction |
—
|
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: rebuilt after World War II destruction | Statement: [Telavåg, hasRebuiltStatus, rebuilt after World War II destruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRebuiltStatus Context triple: [Telavåg, hasRebuiltStatus, rebuilt after World War II destruction]
-
A.
hasRebuilt
chosen
Indicates that an entity has restored, reconstructed, or built again something that previously existed or was damaged or destroyed.
-
B.
hasRebuiltDate
Indicates the date on which something was rebuilt or reconstructed.
-
C.
notRebuiltAfter
Indicates that an entity was destroyed or damaged and has not been reconstructed or restored after a specified event or point in time.
-
D.
hasRebuiltInfrastructure
Indicates that an entity has restored or reconstructed damaged or outdated infrastructure, typically improving or modernizing it in the process.
-
E.
laterRebuiltAs
Indicates that one entity was reconstructed or redeveloped at a later time to become or be replaced by another specific 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.