Triple
T1109485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cant Z.506 Airone |
E25559
|
entity |
| Predicate | enteredServiceAs |
P2339
|
FINISHED |
| Object | Cant Z.506B bomber variant |
—
|
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: Cant Z.506B bomber variant | Statement: [Cant Z.506 Airone, enteredServiceAs, Cant Z.506B bomber variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredServiceAs Context triple: [Cant Z.506 Airone, enteredServiceAs, Cant Z.506B bomber variant]
-
A.
enteredService
chosen
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
enteredSpace
Indicates that an entity has moved into or crossed the boundary into a particular space or area.
-
C.
enteredRAFService
Indicates that an entity began service in the Royal Air Force (RAF).
-
D.
entersFrom
Indicates that one entity moves into or arrives at a place, state, or context by coming from another specified source or location.
-
E.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4ba045fd88190982e1c6278fb9ca3 |
completed | March 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69a4b749e2a881909ef28745a7d2d917 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.