Triple
T9004072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carbon |
E215099
|
entity |
| Predicate | notSupported |
P31509
|
FINISHED |
| Object | 64-bit applications on macOS |
—
|
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: 64-bit applications on macOS | Statement: [Carbon, notSupported, 64-bit applications on macOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notSupported Context triple: [Carbon, notSupported, 64-bit applications on macOS]
-
A.
doNotSupport
Indicates that one entity withholds help, approval, or endorsement from another entity or action.
-
B.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
C.
notCompatibleWith
Indicates that two entities cannot function together properly or are unsuitable for joint use or interaction.
-
D.
notImplementedBy
Indicates that a specified functionality, specification, or feature is *not* realized or provided by the referenced entity (such as a system, component, or implementation).
-
E.
unsupportedPlatform
chosen
Indicates that a given platform is not supported for a particular action, feature, or system.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6959497c8190a748c78504dd2eb6 |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.