Triple
T29198671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Band Instrument Capital of the World |
E740201
|
entity |
| Predicate | appliedToState |
P134515
|
FINISHED |
| Object | Indiana |
—
|
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: Indiana | Statement: [Band Instrument Capital of the World, appliedToState, Indiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToState Context triple: [Band Instrument Capital of the World, appliedToState, Indiana]
-
A.
appliedToStatesThrough
Indicates that something (such as a rule, policy, or process) is implemented or enforced by means of, or via the mediation of, particular states.
-
B.
appliedToStatus
chosen
Indicates that an action, rule, or condition is associated with or affects a particular status or state.
-
C.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
-
D.
appliedWhen
Indicates the condition, time, or circumstances under which something (such as a rule, action, or effect) becomes applicable or is carried out.
-
E.
appliedBefore
Indicates that one action, process, or condition was applied earlier in time than another.
- 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_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 28, 2026, 12:05 p.m.