Triple
T26371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Crossing the Delaware (Leutze) |
E527
|
entity |
| Predicate | narrativeTime |
P302
|
FINISHED |
| Object | night of December 25–26, 1776 |
—
|
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: night of December 25–26, 1776 | Statement: [Washington Crossing the Delaware (Leutze), narrativeTime, night of December 25–26, 1776]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeTime Context triple: [Washington Crossing the Delaware (Leutze), narrativeTime, night of December 25–26, 1776]
-
A.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
C.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
D.
numberOfStories
Indicates the total count of levels or floors that a structure or building has.
-
E.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
| NER | Named-entity recognition | batch_69a247798a348190bb943d38300ae3ef |
completed | Feb. 28, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69a24658749881909117b007ec3d8633 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.