Triple
T10438036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. President |
E246091
|
entity |
| Predicate | usedAtBeginningOf |
P93740
|
FINISHED |
| Object | formal address to the President of Romania |
—
|
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: formal address to the President of Romania | Statement: [Mr. President, usedAtBeginningOf, formal address to the President of Romania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAtBeginningOf Context triple: [Mr. President, usedAtBeginningOf, formal address to the President of Romania]
-
A.
beganWith
Indicates that one event, process, or state started with or was initiated by another specified event, process, or state.
-
B.
usedAsPrefixIn
chosen
Indicates that one element functions as a leading prefix component in the formation or representation of another element.
-
C.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
D.
useBegan
Indicates that an entity initiated or started using another entity or resource at a particular point in time.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe083cd881909d2d8ad75d1d94cb |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:14 p.m.