Triple
T33131111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Learjet 85 |
E847870
|
entity |
| Predicate | primaryDevelopmentSite |
P39881
|
FINISHED |
| Object | Wichita, Kansas |
E149269
|
NE 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: Wichita, Kansas | Statement: [Learjet 85, primaryDevelopmentSite, Wichita, Kansas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDevelopmentSite Context triple: [Learjet 85, primaryDevelopmentSite, Wichita, Kansas]
-
A.
primarySites
chosen
Indicates the main or originating locations associated with an entity, often distinguishing them from secondary or related sites.
-
B.
eraOfPrimaryDevelopment
Indicates the time period during which something was primarily developed or formed.
-
C.
embryologicalOrigin
Indicates that one entity arises from, or is derived from, another entity during embryonic development.
-
D.
embryonicDevelopmentType
Indicates the manner or pattern in which an organism’s embryo develops, including how and where embryonic growth proceeds before birth or hatching.
-
E.
primaryRecordingSite
Indicates the main anatomical or spatial location where a recording or measurement was originally captured.
- F. None of above.
Provenance (4 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a352fb07e148190bd5a6ec89b079b17 |
completed | June 19, 2026, 12:01 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:27 a.m.