Triple
T30405511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal 2 |
E773466
|
entity |
| Predicate | includesExecutableFor |
P127767
|
FINISHED |
| Object | Intel-based Mac |
—
|
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: Intel-based Mac | Statement: [Universal 2, includesExecutableFor, Intel-based Mac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesExecutableFor Context triple: [Universal 2, includesExecutableFor, Intel-based Mac]
-
A.
isExecutedFor
Indicates that an action, plan, or process is carried out on behalf of, or in service of, a particular entity or purpose.
-
B.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
C.
includesExtension
Indicates that one entity contains or incorporates another entity as an added or supplementary extension.
-
D.
canProduceStandaloneExecutable
Indicates that something has the capability to generate a self-contained executable program that can run independently without external dependencies.
-
E.
canBeLoadedBy
chosen
Indicates that one entity is capable of being loaded, initialized, or brought into use by another entity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: April 29, 2026, 8:03 p.m.