Triple
T27053420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark-8 computer |
E684838
|
entity |
| Predicate | kitAvailability |
P161804
|
FINISHED |
| Object | required users to source their own components |
—
|
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: required users to source their own components | Statement: [Mark-8 computer, kitAvailability, required users to source their own components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kitAvailability Context triple: [Mark-8 computer, kitAvailability, required users to source their own components]
-
A.
kitAvailability
chosen
Indicates that a particular kit is available for use, access, or distribution in a given context.
-
B.
packageAvailability
Indicates whether a particular package is currently available for use, access, or distribution.
-
C.
availableWith
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
D.
mayBeAvailableIn
Indicates that an entity has the potential to be obtainable, accessible, or present within a specified context, location, or medium.
-
E.
modernAvailability
Indicates that something is currently obtainable, accessible, or in use in the modern or present-day context.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622b145848190b67cfdc47da6a887 |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:15 a.m.