Triple
T2017153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montclair, Oakland |
E44020
|
entity |
| Predicate | commercialCharacter |
P34516
|
FINISHED |
| Object | village-style business district |
—
|
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: village-style business district | Statement: [Montclair, Oakland, commercialCharacter, village-style business district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialCharacter Context triple: [Montclair, Oakland, commercialCharacter, village-style business district]
-
A.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
B.
commercial
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
C.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
D.
commercialProduct
Indicates that one entity is a product or service offered for sale or commercial use by another entity.
-
E.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
- F. None of above. chosen
Provenance (4 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8ccdb7c81909f6b3c96f79fcdfc |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:38 p.m.