Triple
T29714359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaslui |
E751866
|
entity |
| Predicate | notableHistoricalEventNearby |
P156594
|
FINISHED |
| Object | Battle of Vaslui |
E1306016
|
NE 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: Battle of Vaslui | Statement: [Vaslui, notableHistoricalEventNearby, Battle of Vaslui]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHistoricalEventNearby Context triple: [Vaslui, notableHistoricalEventNearby, Battle of Vaslui]
-
A.
hasNearbyHistoricalEvent
chosen
Indicates that a given entity is located close to the site where a specific historical event occurred.
-
B.
nearbyHistoricalFunction
Indicates that one entity is located close to another entity that has or had a historical role, use, or function.
-
C.
nearHistoricalEventDate
Indicates that something occurs on a date that is close in time to a specified historical event’s date.
-
D.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
-
E.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
- F. None of above.
Provenance (4 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26f1ad976c819085a59a20b650a1f6 |
completed | June 8, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 7:33 p.m.