Triple
T27053423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark-8 computer |
E684838
|
entity |
| Predicate | userAssemblyRequired |
P55766
|
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: [Mark-8 computer, userAssemblyRequired, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userAssemblyRequired Context triple: [Mark-8 computer, userAssemblyRequired, true]
-
A.
assemblyRequired
chosen
Indicates that the associated item or components must be put together or constructed before they can be used.
-
B.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
C.
hadLocalAssembly
Indicates that an entity hosted or possessed a local-level governing or decision-making assembly within its jurisdiction or area.
-
D.
hasAssembler
Indicates that one entity is responsible for assembling, putting together, or constructing another entity.
-
E.
involvedInComplexAssembly
Indicates that an entity participates in the process of assembling or forming a larger molecular or structural complex.
- 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_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:15 a.m.