Triple
T541596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Historic Landmark |
E12640
|
entity |
| Predicate | documentationBy |
P4310
|
FINISHED |
| Object | National Park Service publications |
—
|
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 Park Service publications | Statement: [National Historic Landmark, documentationBy, National Park Service publications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationBy Context triple: [National Historic Landmark, documentationBy, National Park Service publications]
-
A.
documentedBy
chosen
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
B.
legacyDocumentedBy
Indicates that information about a legacy item or concept is recorded or described in a specific documenting source.
-
C.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
D.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
E.
guidedBy
Indicates that an entity’s actions, decisions, or movement are directed, advised, or led by 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_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.