Triple
T36963614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addermire Institute |
E914369
|
entity |
| Predicate | hasKeyLocationType |
P28105
|
FINISHED |
| Object | mission hub |
—
|
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: mission hub | Statement: [Addermire Institute, hasKeyLocationType, mission hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyLocationType Context triple: [Addermire Institute, hasKeyLocationType, mission hub]
-
A.
hasKeyLocation
Indicates that an entity possesses or is associated with a specific primary or important location relevant to it.
-
B.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
C.
hasKeyAgentType
Indicates that an entity is associated with, or characterized by, a primary type of agent responsible for its actions or behavior.
-
D.
hasKeyAssetType
Indicates that an entity possesses or is associated with a specific type or category of key (primary or critical) asset.
-
E.
hasMainLocationType
chosen
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:14 p.m.