Triple
T1257052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British occupation of Philadelphia |
E12416
|
entity |
| Predicate | dateEvacuated |
P5566
|
FINISHED |
| Object | 1778-06-18 |
—
|
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: 1778-06-18 | Statement: [British occupation of Philadelphia, dateEvacuated, 1778-06-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateEvacuated Context triple: [British occupation of Philadelphia, dateEvacuated, 1778-06-18]
-
A.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
-
B.
notableEvacuation
Indicates a significant, widely recognized instance of people being moved or fleeing from a place for safety, typically due to danger or emergency conditions.
-
C.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
D.
dateOfBritishEvacuation
chosen
Indicates the date on which British forces or authorities withdrew from or evacuated a specified place.
-
E.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfa8cfa08190ac49c437a94a843c |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.