Triple
T25769417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temišvar |
E648976
|
entity |
| Predicate | associatedWithEventAtReferencedPlace |
P59649
|
FINISHED |
| Object | start of the 1989 Romanian Revolution |
—
|
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: start of the 1989 Romanian Revolution | Statement: [Temišvar, associatedWithEventAtReferencedPlace, start of the 1989 Romanian Revolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithEventAtReferencedPlace Context triple: [Temišvar, associatedWithEventAtReferencedPlace, start of the 1989 Romanian Revolution]
-
A.
tookPlaceAtEvent
Indicates that an action or occurrence happened during or in the context of a specific event.
-
B.
relativeInvolvedInEvent
Indicates that a person’s relative participates in, is affected by, or is otherwise involved in a particular event.
-
C.
isLinkedToEvent
chosen
Indicates that an entity has an association or connection with a specific event.
-
D.
oftenHeldAtEvent
Indicates that one type of thing frequently takes place or is conducted during a particular event.
-
E.
relationshipToEvent
Indicates the specific way an entity is connected or related to a particular 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: April 22, 2026, 5:13 a.m.