Triple
T36600748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Street Four-Point Approach |
E902906
|
entity |
| Predicate | designPointIncludes |
P199718
|
FINISHED |
| Object | improving physical appearance |
—
|
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: improving physical appearance | Statement: [Main Street Four-Point Approach, designPointIncludes, improving physical appearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designPointIncludes Context triple: [Main Street Four-Point Approach, designPointIncludes, improving physical appearance]
-
A.
gridIncludes
Indicates that a particular grid contains or encompasses a specified element, cell, or sub-region within its structure.
-
B.
containsPoint
Indicates that a geometric region or shape includes a given point within its boundaries.
-
C.
organizationPointIncludes
Indicates that a specific point or location is contained within, or falls under the scope of, an organization’s defined area or domain.
-
D.
previousDesignationIncludes
Indicates that an entity’s earlier or former official name, title, or designation contained the specified value.
-
E.
designLocation
Indicates the place or setting where something is conceived, planned, or designed.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69ff519a67008190b1eda931fdeff53e |
completed | May 9, 2026, 3:24 p.m. |
Created at: May 3, 2026, 4:11 p.m.