Triple
T10679764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | silver pencilled Cochin |
E251712
|
entity |
| Predicate | isBantamVersionAvailable |
P31935
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [silver pencilled Cochin, isBantamVersionAvailable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBantamVersionAvailable Context triple: [silver pencilled Cochin, isBantamVersionAvailable, true]
-
A.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
B.
alsoAvailableInVersion
chosen
Indicates that the same item, feature, or content is offered in another specified version or edition.
-
C.
hasSilentVersion
Indicates that an entity has a corresponding version or variant that is silent or produced without sound.
-
D.
laterVersionsCapability
Indicates that one entity has the capability to support, handle, or be compatible with later versions of another entity.
-
E.
earlierVersionsCapability
Indicates that an entity has the ability to access, handle, or interact with earlier versions of another entity or resource.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc03dc4819080a6211a2bfaaf0a |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.