Triple
T247453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Asian Association for Regional Cooperation |
E5067
|
entity |
| Predicate | SAFTASignedOn |
P4326
|
FINISHED |
| Object | 2004-01-06 |
—
|
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: 2004-01-06 | Statement: [South Asian Association for Regional Cooperation, SAFTASignedOn, 2004-01-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SAFTASignedOn Context triple: [South Asian Association for Regional Cooperation, SAFTASignedOn, 2004-01-06]
-
A.
signedDuring
chosen
Indicates that an agreement, document, or contract was signed within a specified time period or during a particular event.
-
B.
signedByRepresentativeOf
Indicates that an item (such as a document or agreement) has been signed on behalf of a party by that party’s authorized representative.
-
C.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
D.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
-
E.
placeSigned
Indicates that an entity has signed or endorsed a document, agreement, or item at a particular place or location.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d154ebc819087a5c9dc4f62ff44 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.