Triple
T6105033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 10 Squadron RAF |
E136095
|
entity |
| Predicate | primaryBaseType |
P32473
|
FINISHED |
| Object | air base |
—
|
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: air base | Statement: [No. 10 Squadron RAF, primaryBaseType, air base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBaseType Context triple: [No. 10 Squadron RAF, primaryBaseType, air base]
-
A.
baseType
chosen
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
B.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
C.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
-
D.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
E.
typeOfPrimacy
Indicates that one entity holds a primary, leading, or most important status or precedence over others in a given context.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b7ee8b48190b87f5ec8a46d6e2d |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.