Triple
T4884355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Charter Chapter VI |
E109403
|
entity |
| Predicate | listsMeans |
P59610
|
FINISHED |
| Object | negotiation |
—
|
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: negotiation | Statement: [United Nations Charter Chapter VI, listsMeans, negotiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listsMeans Context triple: [United Nations Charter Chapter VI, listsMeans, negotiation]
-
A.
listType
Indicates that one entity specifies the classification or category type of a list associated with another entity.
-
B.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
C.
listsGrounds
Indicates that one entity enumerates or specifies the reasons, bases, or justifications (grounds) associated with another entity.
-
D.
isListedBy
Indicates that one entity appears as an item or entry in a list, catalog, or register maintained or provided by another entity.
-
E.
listingType
Indicates the category or format under which an item, property, or service is offered or advertised (e.g., for sale, for rent, auction, etc.).
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6de253ac8190b1112da6953fa4f2 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6d5976a081909090c0c263f6e9b7 |
completed | March 20, 2026, 3:52 p.m. |
Created at: March 20, 2026, 1:27 p.m.