Triple
T15762694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enipeus River |
E382136
|
entity |
| Predicate | hasNotableNearbyEvent |
P45864
|
FINISHED |
| Object | ancient battles near Pharsalus |
—
|
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: ancient battles near Pharsalus | Statement: [Enipeus River, hasNotableNearbyEvent, ancient battles near Pharsalus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableNearbyEvent Context triple: [Enipeus River, hasNotableNearbyEvent, ancient battles near Pharsalus]
-
A.
hasNearbyEvent
chosen
Indicates that an event occurs close in space or time to the referenced entity.
-
B.
hasNotableNearbyEntity
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
C.
hasNearbyEventType
Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
-
D.
hasNotablePersonEvent
Indicates that there exists a significant event in which the person plays a notable or central role.
-
E.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b6c9fc8190a1bcf763c4b04b12 |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.