Triple
T16742028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letters patent |
E406855
|
entity |
| Predicate | formIncludes |
P12776
|
FINISHED |
| Object | preamble stating authority |
—
|
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: preamble stating authority | Statement: [Letters patent, formIncludes, preamble stating authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formIncludes Context triple: [Letters patent, formIncludes, preamble stating authority]
-
A.
containsForm
chosen
Indicates that one entity includes or encapsulates another entity as a form, structure, or representation within it.
-
B.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
-
C.
includesWildForm
Indicates that something contains or encompasses a wild or non-domesticated form of another entity.
-
D.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside another entity.
-
E.
usesForm
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3f49808190b543d8da34031f3d |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.