Triple
T34187881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Seal of Queensland |
E877011
|
entity |
| Predicate | appliesToDocumentType |
P65896
|
FINISHED |
| Object | letters patent |
—
|
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: letters patent | Statement: [Great Seal of Queensland, appliesToDocumentType, letters patent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToDocumentType Context triple: [Great Seal of Queensland, appliesToDocumentType, letters patent]
-
A.
belongsToDocumentType
chosen
Indicates that one entity is classified under, or associated with, a specific document type.
-
B.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
C.
worksOnDocumentType
Indicates that an entity is involved in handling, processing, or performing tasks related to a specific type or category of document.
-
D.
appliesToObjectType
Indicates that something (such as a rule, constraint, or operation) is specifically relevant or applicable to a particular type or class of object.
-
E.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: May 1, 2026, 1:55 a.m.