Triple
T8471693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Font Manager |
E200293
|
entity |
| Predicate | alsoAccessibleFrom |
P83497
|
FINISHED |
| Object | C language on Macintosh |
—
|
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: C language on Macintosh | Statement: [Font Manager, alsoAccessibleFrom, C language on Macintosh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoAccessibleFrom Context triple: [Font Manager, alsoAccessibleFrom, C language on Macintosh]
-
A.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
B.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
-
C.
isAccessible
Indicates that one entity can be reached, used, or entered by another entity without obstruction or restriction.
-
D.
accessibleAs
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
-
E.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f3a81881908f20514579945ffa |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:11 p.m.