Triple
T37857912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Mills Ford |
E944241
|
entity |
| Predicate | dateOfMilitaryUse |
P15394
|
FINISHED |
| Object | July 21, 1861 |
—
|
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: July 21, 1861 | Statement: [Union Mills Ford, dateOfMilitaryUse, July 21, 1861]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfMilitaryUse Context triple: [Union Mills Ford, dateOfMilitaryUse, July 21, 1861]
-
A.
militaryUseEnd
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
-
B.
firstCombatUseDate
Indicates the date on which something (typically a weapon, system, or tactic) was first used in actual combat.
-
C.
eraOfPrimaryMilitaryUse
Indicates the historical time period during which the subject was primarily used for military purposes.
-
D.
hasMilitarySignificanceSince
chosen
Indicates that something has held military importance or strategic value starting from a specified point in time.
-
E.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 3, 2026, 4:19 p.m.