Triple
T21593013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 102 of the Charter of the United Nations |
E532825
|
entity |
| Predicate | hasTwoParagraphStructure |
P25345
|
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: [Article 102 of the Charter of the United Nations, hasTwoParagraphStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTwoParagraphStructure Context triple: [Article 102 of the Charter of the United Nations, hasTwoParagraphStructure, true]
-
A.
hasTwoParagraphs
chosen
Indicates that the related content or text is composed of exactly two distinct paragraphs.
-
B.
hasParagraph
Indicates that one entity contains or is associated with a specific paragraph as part of its content or structure.
-
C.
hasNumberOfParagraphs
Indicates that an entity is associated with a specific count of paragraphs it contains or comprises.
-
D.
hasTwoPartStructure
Indicates that something is composed of exactly two distinct, structured parts that together form a whole.
-
E.
hasArticleStructure
Indicates that one entity possesses or follows a specific article-like structural organization (e.g., sections, headings, or layout).
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefadeb56c8190bce79efadf3c644d |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:32 p.m.