Triple
T29714359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaslui |
E751866
|
entity |
| Predicate | notableHistoricalEventNearby |
—
|
GENERATED |
| Object | Battle of Vaslui |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: April 28, 2026, 7:33 p.m.