Triple
T14393172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CHI |
E356893
|
entity |
| Predicate | typicalLocationPattern |
P8688
|
FINISHED |
| Object | rotating international locations |
—
|
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: rotating international locations | Statement: [CHI, typicalLocationPattern, rotating international locations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationPattern Context triple: [CHI, typicalLocationPattern, rotating international locations]
-
A.
locationPattern
chosen
Indicates a recurring or structured spatial relationship, where an entity consistently appears or is arranged in a particular type of location or spatial configuration.
-
B.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
-
C.
typicalOnsetLocation
Indicates the anatomical location where a condition, symptom, or process most commonly begins or first appears.
-
D.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
E.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de902b9acc8190817ffa848a76a880 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.