Triple
T25672634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohrid Framework Agreement |
E643718
|
entity |
| Predicate | signedByMediator |
P37021
|
FINISHED |
| Object | François Léotard |
—
|
NE NERFINISHED |
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: François Léotard | Statement: [Ohrid Framework Agreement, signedByMediator, François Léotard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedByMediator Context triple: [Ohrid Framework Agreement, signedByMediator, François Léotard]
-
A.
agreementSignedBy
chosen
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
B.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
C.
signGivenBy
Indicates that a sign (such as a signal, gesture, or indication) is produced or provided by one entity to another.
-
D.
signedBefore
Indicates that one signing event occurred earlier in time than another signing event.
-
E.
signedTo
Indicates that one entity has formally entered into a contract or agreement with another, typically for representation, employment, or services.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3389ac819092997022ed2bc2f8 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 7:30 p.m.