Triple
T36410951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorus (Henry V) |
E896876
|
entity |
| Predicate | workSettingSecondaryLocation |
P62757
|
FINISHED |
| Object | England |
—
|
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: England | Statement: [Chorus (Henry V), workSettingSecondaryLocation, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workSettingSecondaryLocation Context triple: [Chorus (Henry V), workSettingSecondaryLocation, England]
-
A.
additionalLocation
Indicates that an entity has one or more extra or secondary locations associated with it beyond its primary location.
-
B.
subsidiaryLocation
Indicates that one entity is located in, or operates as a subsidiary within, the geographic or organizational area defined by another entity.
-
C.
secondarySite
Indicates that one entity serves as an additional or subordinate location associated with another primary site.
-
D.
secondarySetting
chosen
Indicates that an entity serves as an additional or supporting setting context for another entity, rather than being the primary setting.
-
E.
hasSecondaryCity
Indicates that an entity possesses or is associated with a secondary city in addition to its primary city.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:10 p.m.