Triple
T3384941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley Forge National Historical Park |
E71276
|
entity |
| Predicate | significantEventStartDate |
P288
|
FINISHED |
| Object | December 1777 |
—
|
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: December 1777 | Statement: [Valley Forge National Historical Park, significantEventStartDate, December 1777]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantEventStartDate Context triple: [Valley Forge National Historical Park, significantEventStartDate, December 1777]
-
A.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
-
B.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
C.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
E.
eventStartDateOrganized
Indicates the date on which an event is formally scheduled or organized to begin.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5ee5e188190912dcea494a12038 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.