Triple
T27976499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Air Force (early, non-permanent) |
E706503
|
entity |
| Predicate | usedPersonnelFrom |
P93505
|
FINISHED |
| Object | former World War I airmen |
—
|
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: former World War I airmen | Statement: [Canadian Air Force (early, non-permanent), usedPersonnelFrom, former World War I airmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPersonnelFrom Context triple: [Canadian Air Force (early, non-permanent), usedPersonnelFrom, former World War I airmen]
-
A.
usedByPerson
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
-
B.
usedLabourFrom
chosen
Indicates that one entity employed or made use of the labor or work effort provided by another entity.
-
C.
transferredPersonnelTo
Indicates that one entity moved or reassigned personnel from itself to another entity.
-
D.
personnel
Indicates that an entity serves as staff or workforce associated with another entity, such as an organization, project, or facility.
-
E.
usedEquipmentFrom
Indicates that one entity has utilized or operated equipment that originated from or was provided by another 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:41 p.m.