Triple
T33051437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGHH |
E845732
|
entity |
| Predicate | identifiesType |
P56511
|
FINISHED |
| Object | aerodrome |
—
|
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: aerodrome | Statement: [EGHH, identifiesType, aerodrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesType Context triple: [EGHH, identifiesType, aerodrome]
-
A.
identifiesEntityType
chosen
Indicates that one entity specifies or determines the type or category to which another entity belongs.
-
B.
InType
Indicates that an entity belongs to, is categorized under, or is an instance of a specified type or class.
-
C.
typeOfDiscrimination
Indicates a relationship where one party is subjected to a specific kind or category of discriminatory treatment by another party or within a given context.
-
D.
typeOfIdentity
Indicates the specific category or nature of identity that characterizes or defines an entity within a given context.
-
E.
seeType
Indicates that one entity observes, recognizes, or visually perceives another entity of a particular type or category.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:24 a.m.