Triple
T34151961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Seal of Victoria |
E876022
|
entity |
| Predicate | sealFor |
P94983
|
FINISHED |
| Object | State of Victoria |
—
|
NE NERFINISHED |
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: State of Victoria | Statement: [Great Seal of Victoria, sealFor, State of Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sealFor Context triple: [Great Seal of Victoria, sealFor, State of Victoria]
-
A.
seal
Indicates that an agent closes or fastens something so that it is securely shut and often airtight or watertight.
-
B.
sealType
Indicates the specific kind or category of seal associated with an entity or connection.
-
C.
sealedBy
Indicates that one entity is closed, secured, or made airtight/watertight through the action or presence of another entity.
-
D.
isSealOf
chosen
Indicates that one entity serves as the official seal, emblem, or stamp that authenticates, endorses, or formally represents another entity.
-
E.
usedSeal
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.