Triple
T8676945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karup |
E205937
|
entity |
| Predicate | hasTypeOfBase |
P16808
|
FINISHED |
| Object | air force 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 force base | Statement: [Karup, hasTypeOfBase, air force base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfBase Context triple: [Karup, hasTypeOfBase, air force base]
-
A.
hasTypeOfReference
Indicates that one entity uses or is associated with a particular kind or category of reference (such as a citation, pointer, or referential link) to another entity.
-
B.
hasBaseISA
Indicates that an entity’s base or fundamental type is a specified ISA (Instruction Set Architecture) or foundational classification.
-
C.
hasRootType
Indicates that an entity possesses or is associated with a primary or fundamental type that serves as its root classification.
-
D.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
isBaseFor
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.