Triple
T31681830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Lanka Air Force |
E808555
|
entity |
| Predicate | dateRenamedToCurrentName |
P115495
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Sri Lanka Air Force, dateRenamedToCurrentName, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRenamedToCurrentName Context triple: [Sri Lanka Air Force, dateRenamedToCurrentName, 1972]
-
A.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
B.
renamedTo
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
C.
reestablishedUnderCurrentName
Indicates that an entity previously existed under a different name and was later reestablished using its current name.
-
D.
renamedInPeriod
chosen
Indicates that an entity underwent a renaming during a specified time period.
-
E.
relocatedAndRenamed
Indicates that an entity has moved from one location to another and changed its name as part of that move.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:05 p.m.