Triple
T940889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Hall National Memorial |
E20301
|
entity |
| Predicate | hasNationalParkServiceUnitCode |
P21993
|
FINISHED |
| Object | FEHA |
—
|
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: FEHA | Statement: [Federal Hall National Memorial, hasNationalParkServiceUnitCode, FEHA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNationalParkServiceUnitCode Context triple: [Federal Hall National Memorial, hasNationalParkServiceUnitCode, FEHA]
-
A.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
B.
hasNationalForest
Indicates that a place or jurisdiction contains, includes, or is home to at least one designated national forest.
-
C.
withinNationalPark
Indicates that one entity is located inside the geographic boundaries of a national park designated by another entity.
-
D.
hasNationalParkSystem
Indicates that a country or region maintains an organized, officially designated system of national parks under its governance.
-
E.
hasRegionalPark
Indicates that a place or administrative area contains or is served by a designated regional park.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b38cc6888190b1d9043ec8fbcbc3 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b344f6f48190ba03ce593c94176b |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.