Triple
T34255669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Declaration on the Doctrine of Justification |
E878869
|
entity |
| Predicate | hasFollowUpDocument |
P32415
|
FINISHED |
| Object | Annex to the Official Common Statement |
—
|
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: Annex to the Official Common Statement | Statement: [Joint Declaration on the Doctrine of Justification, hasFollowUpDocument, Annex to the Official Common Statement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFollowUpDocument Context triple: [Joint Declaration on the Doctrine of Justification, hasFollowUpDocument, Annex to the Official Common Statement]
-
A.
hasCompanionDocument
Indicates that one document is associated with and serves as a companion to another document.
-
B.
followUpNeeded
Indicates that an additional action, check, or communication is required after an initial event or interaction.
-
C.
followsUp
chosen
Indicates that one entity continues, responds to, or builds upon a previous entity, typically as a subsequent action, communication, or step.
-
D.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
E.
isFollowUpToSingle
Indicates that one event, message, or action directly continues or responds to a single specific prior event, message, or action.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:56 a.m.