Triple
T18372057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTEA |
E446204
|
entity |
| Predicate | extendsExistingTermsBy |
P9926
|
FINISHED |
| Object | 20 years |
—
|
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: 20 years | Statement: [CTEA, extendsExistingTermsBy, 20 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsExistingTermsBy Context triple: [CTEA, extendsExistingTermsBy, 20 years]
-
A.
extendedBy
chosen
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
-
B.
extendsBetween
Indicates a relationship where one entity spans or stretches from one point, object, or boundary to another, covering the space between them.
-
C.
extendsUnder
Indicates that one entity physically stretches or reaches out beneath another entity, occupying a lower position while continuing under its span or area.
-
D.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
-
E.
extendedPassagesFrom
Indicates that one text or document contains longer or more detailed passages derived from, elaborating on, or continuing the content of another source.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51754539c819083f13b85cacb6cce |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:44 a.m.