Triple
T35827327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morton’s Ford |
E1035683
|
entity |
| Predicate | sawMajorActionOnDate |
P49061
|
FINISHED |
| Object | February 6, 1864 |
—
|
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: February 6, 1864 | Statement: [Morton’s Ford, sawMajorActionOnDate, February 6, 1864]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawMajorActionOnDate Context triple: [Morton’s Ford, sawMajorActionOnDate, February 6, 1864]
-
A.
sawActionDuring
Indicates that one entity observed an action or event occurring within a specific time period or during another event.
-
B.
sawActionOn
Indicates that one entity visually perceived another entity performing an action.
-
C.
sawMajorOperationsBy
Indicates that the subject entity experienced or witnessed significant or large-scale operations carried out by the object entity.
-
D.
notableActionAt
Indicates that an entity performed or was involved in a significant action or event at a specific location or point in time.
-
E.
notableOperationDate
chosen
Indicates the date on which a significant or noteworthy operation, event, or activity associated with an entity took place.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.