Triple
T2562053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commission on Chicago Landmarks |
E57262
|
entity |
| Predicate | usesCriteria |
P36515
|
FINISHED |
| Object | historical significance |
—
|
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: historical significance | Statement: [Commission on Chicago Landmarks, usesCriteria, historical significance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCriteria Context triple: [Commission on Chicago Landmarks, usesCriteria, historical significance]
-
A.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
evaluationCriteriaInclude
chosen
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
C.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
-
D.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
-
E.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.