Triple
T36600746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Street Four-Point Approach |
E902906
|
entity |
| Predicate | promotionPointIncludes |
P117414
|
FINISHED |
| Object | marketing the downtown |
—
|
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: marketing the downtown | Statement: [Main Street Four-Point Approach, promotionPointIncludes, marketing the downtown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionPointIncludes Context triple: [Main Street Four-Point Approach, promotionPointIncludes, marketing the downtown]
-
A.
promotionIncludes
chosen
Indicates that a particular promotion encompasses, covers, or applies to a specified item, service, or condition.
-
B.
promotionConditions
Indicates the conditions or criteria that must be met for a promotion to occur between entities.
-
C.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
D.
promotionChoiceWith
Indicates that one entity is involved in selecting or determining a promotional option together with another entity.
-
E.
promotionInvolved
Indicates that an entity participated in or was associated with a promotional activity, campaign, or marketing effort.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.