Triple
T27213479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand Article XV squadron |
E684065
|
entity |
| Predicate | basedOnPersonnelFrom |
P51517
|
FINISHED |
| Object | Royal New Zealand Air Force |
—
|
NE NERFINISHED |
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: Royal New Zealand Air Force | Statement: [New Zealand Article XV squadron, basedOnPersonnelFrom, Royal New Zealand Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnPersonnelFrom Context triple: [New Zealand Article XV squadron, basedOnPersonnelFrom, Royal New Zealand Air Force]
-
A.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
B.
basedOnWorkDirector
Indicates that one entity serves as the director of a work on which another entity is based.
-
C.
personnelSource
chosen
Indicates the origin or provider from which personnel are obtained or assigned.
-
D.
basedOnPersona
Indicates that something is created, customized, or decided according to a specific persona’s characteristics, preferences, or profile.
-
E.
basedOnName
Indicates that one entity is derived, determined, or identified using the name of 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 9:40 a.m.