Triple
T29198670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Band Instrument Capital of the World |
E740201
|
entity |
| Predicate | appliedToPlace |
P78509
|
FINISHED |
| Object | Elkhart |
—
|
NE NERFINISHED |
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: Elkhart | Statement: [Band Instrument Capital of the World, appliedToPlace, Elkhart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToPlace Context triple: [Band Instrument Capital of the World, appliedToPlace, Elkhart]
-
A.
hasPlaceIn
chosen
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
-
B.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
C.
designedToPlace
Indicates that something is intentionally created or configured for the purpose of positioning or setting another entity in a specific place or arrangement.
-
D.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
-
E.
appliesToPosition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 28, 2026, 12:05 p.m.