Triple
T26448579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Oaken Bucket |
E665277
|
entity |
| Predicate | linkInscription |
P160761
|
FINISHED |
| Object | IP for tied games |
—
|
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: IP for tied games | Statement: [Old Oaken Bucket, linkInscription, IP for tied games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkInscription Context triple: [Old Oaken Bucket, linkInscription, IP for tied games]
-
A.
linkInscription
chosen
Indicates a relationship where an inscription is associated with, or serves as a reference to, another entity such as a document, object, or record.
-
B.
issuedInscription
Indicates that an authority or source formally created and released a specific inscription or written record.
-
C.
issuedInscriptionsIn
Indicates that an entity (such as an authority or issuer) produced or authorized inscriptions within a specified place or context.
-
D.
linkedAward
Indicates that one award is associated with, connected to, or references another award in a meaningful way.
-
E.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6126357188190afe38ad815bc4bab |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 12:03 a.m.