Triple
T30405446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac OS X on Intel |
E773464
|
entity |
| Predicate | laterCoexistsWith |
P198416
|
FINISHED |
| Object | macOS on Apple silicon |
—
|
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: macOS on Apple silicon | Statement: [Mac OS X on Intel, laterCoexistsWith, macOS on Apple silicon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCoexistsWith Context triple: [Mac OS X on Intel, laterCoexistsWith, macOS on Apple silicon]
-
A.
laterCorrespondsTo
Indicates that one entity corresponds to, matches, or is the counterpart of another entity that occurs or is defined at a later time or stage.
-
B.
existedAfter
Indicates that one entity came into existence only after another entity already existed.
-
C.
laterExtendedIn
Indicates that an existing entity (such as a work, version, or specification) was subsequently expanded, updated, or built upon by a later entity.
-
D.
laterBasedOn
Indicates that one event, state, or version occurs or is established after another, using the earlier one as its basis or reference point.
-
E.
laterComplementedBy
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later entity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
| PDg | Predicate description generation | batch_69fee25c7c548190a2c6e50074a33da4 |
completed | May 9, 2026, 7:29 a.m. |
Created at: April 29, 2026, 8:03 p.m.