Triple
T8414506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac 68k bootloaders |
E198700
|
entity |
| Predicate | runsAfter |
P9424
|
FINISHED |
| Object | Macintosh 68k ROM startup code |
—
|
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: Macintosh 68k ROM startup code | Statement: [Mac 68k bootloaders, runsAfter, Macintosh 68k ROM startup code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsAfter Context triple: [Mac 68k bootloaders, runsAfter, Macintosh 68k ROM startup code]
-
A.
runsWith
Indicates that one entity runs together alongside another entity, typically at the same time and place.
-
B.
classAfter
Indicates that one class or course occurs later in time or sequence than another class or course.
-
C.
laterFunction
chosen
Indicates that one function or event occurs after another in time.
-
D.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
-
E.
appliesToAfter
Indicates that one entity becomes relevant or applicable only after another specified event, condition, or time has occurred.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e328cc8190b3b038005d0bb66f |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.