Triple
T410294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Covenant on Economic, Social and Cultural Rights |
E9473
|
entity |
| Predicate | preamblePresent |
P13122
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [International Covenant on Economic, Social and Cultural Rights, preamblePresent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preamblePresent Context triple: [International Covenant on Economic, Social and Cultural Rights, preamblePresent, true]
-
A.
preambleBeginsWith
Indicates that the preamble of a document or text starts with a specified substring, phrase, or content.
-
B.
preambleRecalls
Indicates that a preamble references or brings back into consideration a prior statement, event, or context.
-
C.
hasPrefaceBy
Indicates that a work includes a preface written by a specified person.
-
D.
fieldPresenceIn
Indicates that something exists or is located within a particular field, area, or domain.
-
E.
pretext
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
- F. None of above. chosen
Provenance (4 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ed3032148190beb3a516e437f8f8 |
completed | Feb. 28, 2026, 1:27 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.