Triple
T541591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Historic Landmark |
E12640
|
entity |
| Predicate | hasDesignationLevel |
P14125
|
FINISHED |
| Object | national level |
—
|
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: national level | Statement: [National Historic Landmark, hasDesignationLevel, national level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignationLevel Context triple: [National Historic Landmark, hasDesignationLevel, national level]
-
A.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
B.
designationLevel
chosen
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
C.
hasLetterDesignation
Indicates that an entity is assigned or associated with a specific letter-based designation or code.
-
D.
canBeDesignatedBy
Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
-
E.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49861195081909540eaf402a5401a |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b67c308190a1a225ab7c4b74c6 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.