Triple
T3505666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of the United Kingdom |
E74069
|
entity |
| Predicate | writtenInSingleDocument |
P48376
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Constitution of the United Kingdom, writtenInSingleDocument, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenInSingleDocument Context triple: [Constitution of the United Kingdom, writtenInSingleDocument, no]
-
A.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
B.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
C.
writtenInSameManuscriptAs
Indicates that two written works or textual items appear together within the same physical or digital manuscript.
-
D.
usedDocument
Indicates that one entity has employed, referenced, or otherwise made use of a particular document in performing an action or fulfilling a purpose.
-
E.
standardDocument
Indicates that an entity is a formal, authoritative document that defines standard specifications, rules, or guidelines to be followed.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf38e988190998d722b95830411 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:18 p.m.