Triple
T1774313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classic Environment |
E38943
|
entity |
| Predicate | emulationType |
P842
|
FINISHED |
| Object | API-level compatibility layer |
—
|
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: API-level compatibility layer | Statement: [Classic Environment, emulationType, API-level compatibility layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emulationType Context triple: [Classic Environment, emulationType, API-level compatibility layer]
-
A.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
B.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
C.
hasPlatformType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
D.
simType
Indicates that two entities share the same or a comparable type, category, or classification.
-
E.
neuralEngineType
Indicates the specific kind or category of neural processing engine associated with or used by an 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab17e368048190b7b73d156400f772 |
completed | March 6, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69aa61cd4c1c8190a8dff391f5642bfe |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.