Triple
T29315930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North West Frontier (film score) |
E743375
|
entity |
| Predicate | basedOnSettingIn |
P62477
|
FINISHED |
| Object | India |
—
|
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: India | Statement: [North West Frontier (film score), basedOnSettingIn, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnSettingIn Context triple: [North West Frontier (film score), basedOnSettingIn, India]
-
A.
basedOnSetting
chosen
Indicates that one entity is derived from, influenced by, or constructed using the setting or contextual environment defined by another entity.
-
B.
basedInSetting
Indicates that an entity is situated, located, or primarily operates within a particular setting or environment.
-
C.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
D.
basedOnValues
Indicates that something is determined, derived, or decided according to specified values or value-based criteria.
-
E.
basedOnStrategyOf
Indicates that one entity’s strategy is derived from, influenced by, or constructed using the strategy of another entity.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 28, 2026, 1:19 p.m.