Triple
T24581651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 8 Squadron RAF |
E608266
|
entity |
| Predicate | longServing |
P119937
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [No. 8 Squadron RAF, longServing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longServing Context triple: [No. 8 Squadron RAF, longServing, true]
-
A.
longLived
chosen
Indicates that an entity has a lifespan or duration of existence significantly longer than what is typical or expected in its context.
-
B.
laterServedIn
Indicates that one entity subsequently held a service position or role in which another entity had previously served.
-
C.
longType
Indicates that something has a length-related classification or is characterized by being of extended duration or distance.
-
D.
servedByAtAllTimes
Indicates that one entity continuously provides service or support to another entity without interruption over the entire relevant time period.
-
E.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a982db00819081038adce05c0b52 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.