Triple
T13491084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agreement on Textiles and Clothing |
E318632
|
entity |
| Predicate | startOfTransitionPeriod |
P30990
|
FINISHED |
| Object | 1 January 1995 |
—
|
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: 1 January 1995 | Statement: [Agreement on Textiles and Clothing, startOfTransitionPeriod, 1 January 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfTransitionPeriod Context triple: [Agreement on Textiles and Clothing, startOfTransitionPeriod, 1 January 1995]
-
A.
establishedTransitionPeriod
chosen
Indicates that an entity has formally set or defined a specific transition period between two states, conditions, or arrangements.
-
B.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
C.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
-
D.
recordedInPeriodStart
Indicates that an event or record began or was first documented at the start of a specified time period.
-
E.
focusPeriodStart
Indicates the point in time at which a specified focus period or interval begins.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3cbe2081908c6792362c67c8f1 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.