Triple
T3013401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agreement on Textiles and Clothing |
E82275
|
entity |
| Predicate | finalIntegrationDate |
P6972
|
FINISHED |
| Object | 2005-01-01 |
—
|
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: 2005-01-01 | Statement: [Agreement on Textiles and Clothing, finalIntegrationDate, 2005-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalIntegrationDate Context triple: [Agreement on Textiles and Clothing, finalIntegrationDate, 2005-01-01]
-
A.
integrationDate
chosen
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
B.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
C.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
-
D.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
E.
lastEntryDate
Indicates the date on which the most recent entry, record, or update associated with the subject occurred.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a6883c081909b6b74f078e347b7 |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.