Triple
T15969717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albatros C.I |
E387287
|
entity |
| Predicate | operatorPosition |
P89365
|
FINISHED |
| Object | observer in rear cockpit |
—
|
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: observer in rear cockpit | Statement: [Albatros C.I, operatorPosition, observer in rear cockpit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorPosition Context triple: [Albatros C.I, operatorPosition, observer in rear cockpit]
-
A.
usesOperatorPosition
chosen
Indicates that one entity occupies or is assigned to the role of an operator within a particular position or context.
-
B.
operatorOfLocation
Indicates that an entity operates, manages, or runs a particular location or facility.
-
C.
operator
Indicates that one entity functions as the operator (controller or handler) of another entity, such as a system, device, or process.
-
D.
locationOfOperator
Indicates the place or position where an operator is situated or performs its function.
-
E.
operatorBase
Indicates that one entity serves as the primary or foundational operator for another entity or operation.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.