Triple
T7474136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motor Row District |
E176585
|
entity |
| Predicate | primaryUseDuringPeak |
P35920
|
FINISHED |
| Object | automobile sales |
—
|
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: automobile sales | Statement: [Motor Row District, primaryUseDuringPeak, automobile sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseDuringPeak Context triple: [Motor Row District, primaryUseDuringPeak, automobile sales]
-
A.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
B.
peakUse
chosen
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
C.
leaderDuringPeak
Indicates that an entity served as the primary leader of another entity during the latter’s peak or most successful period.
-
D.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
E.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f417fbb48190b134eaf1da1b4289 |
completed | March 27, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:41 p.m.