Triple
T26817891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ann-Marie |
E675166
|
entity |
| Predicate | settingDescriptor |
P25484
|
FINISHED |
| Object | contemporary London |
—
|
LITERAL 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: contemporary London | Statement: [Ann-Marie, settingDescriptor, contemporary London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingDescriptor Context triple: [Ann-Marie, settingDescriptor, contemporary London]
-
A.
settingDescription
chosen
Indicates the descriptive details or characteristics that define the context or environment in which something occurs.
-
B.
settingControlled
Indicates that one entity regulates, adjusts, or determines the configuration or parameters of another entity.
-
C.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
D.
indicatedSetting
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another entity.
-
E.
settingChange
Indicates a change made to a configuration, environment, or parameter value from one state to 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 4:53 a.m.