Triple
T37604696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Historic Landmarks in Ohio |
E935614
|
entity |
| Predicate | nominationInitiatedBy |
P190411
|
FINISHED |
| Object | property owners |
—
|
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: property owners | Statement: [National Historic Landmarks in Ohio, nominationInitiatedBy, property owners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nominationInitiatedBy Context triple: [National Historic Landmarks in Ohio, nominationInitiatedBy, property owners]
-
A.
nominationReceivedBy
Indicates that an entity has received a nomination from another entity or source.
-
B.
nomineeOf
Indicates that one entity is a candidate put forward or selected for an award, position, or recognition by another entity.
-
C.
nominatedFrom
Indicates that an entity has been put forward or proposed as a candidate originating from a particular source, group, or jurisdiction.
-
D.
nominated
Indicates that one entity formally proposes or selects another entity for a position, role, award, or recognition.
-
E.
nominationOutcome
Indicates the result or status that a nomination process yields for a candidate or entity.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:18 p.m.