Triple
T27070075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article XIII of the Wisconsin Constitution |
E685298
|
entity |
| Predicate | isMiscellaneousArticle |
P6001
|
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 XIII of the Wisconsin Constitution, isMiscellaneousArticle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMiscellaneousArticle Context triple: [Article XIII of the Wisconsin Constitution, isMiscellaneousArticle, true]
-
A.
containsArticle
Indicates that one entity includes or holds an article (such as a written piece, item, or document) as part of its contents.
-
B.
articleType
chosen
Indicates the specific category or kind of article associated with an entity.
-
C.
hasSeparateArticleFrom
Indicates that two related topics are covered in distinct, standalone articles rather than within the same article.
-
D.
containsArticleOn
Indicates that one entity includes or features an article about another entity within its content or collection.
-
E.
typicalArticle
Indicates that one entity is a standard, representative, or commonly occurring instance of the type or category denoted by the other entity.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623107cf08190af1660cd6987c912 |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:27 a.m.