Triple
T4617251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boot Record Volume Descriptor |
E100896
|
entity |
| Predicate | hasTypeCode |
P56964
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Boot Record Volume Descriptor, hasTypeCode, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeCode Context triple: [Boot Record Volume Descriptor, hasTypeCode, 0]
-
A.
hasCommunicationCodeType
Indicates that an entity is associated with a specific type or category of communication code (e.g., phone, fax, email, messaging).
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasISOCodeType
Indicates that an entity is associated with a specific type or category of ISO code (e.g., country code, currency code, language code).
-
D.
hasCodaTypes
Indicates that a linguistic unit (such as a syllable) possesses one or more specific types of codas in its structure.
-
E.
hasStandardType
Indicates that something conforms to or is categorized under a defined standard classification or type.
- F. None of above. chosen
Provenance (4 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:12 p.m.