Triple
T6898624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Landmark |
E159435
|
entity |
| Predicate | resultOfDesignation |
P974
|
FINISHED |
| Object | listing as a Boston Landmark |
—
|
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: listing as a Boston Landmark | Statement: [Boston Landmark, resultOfDesignation, listing as a Boston Landmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfDesignation Context triple: [Boston Landmark, resultOfDesignation, listing as a Boston Landmark]
-
A.
decisionMakerForDesignation
Indicates that one entity has the authority or responsibility to make or approve decisions regarding the designation or assignment of another entity.
-
B.
hasDesignation
chosen
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
C.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
-
D.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
-
E.
designationFor
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95d67448190857f36b8115b03f6 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.