Triple
T20080035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gubaru |
E499972
|
entity |
| Predicate | eventRoleDescription |
P4073
|
FINISHED |
| Object | led or facilitated entry of Persian forces into Babylon |
—
|
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: led or facilitated entry of Persian forces into Babylon | Statement: [Gubaru, eventRoleDescription, led or facilitated entry of Persian forces into Babylon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventRoleDescription Context triple: [Gubaru, eventRoleDescription, led or facilitated entry of Persian forces into Babylon]
-
A.
eventRole
chosen
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
B.
organizerRole
Indicates that an entity has the role or responsibility of organizing an event, activity, or group.
-
C.
eventDescription
Indicates that a textual summary or explanation is provided describing what happens in the event.
-
D.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
E.
eventManagement
Indicates the organization, coordination, and oversight of all activities and resources involved in planning and executing an 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643f93208190ae2a413f88ea9aed |
completed | April 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.