Triple
T28582898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zephyr |
E723423
|
entity |
| Predicate | supportsPOSIXAPIs |
P202969
|
FINISHED |
| Object | partial |
—
|
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: partial | Statement: [Zephyr, supportsPOSIXAPIs, partial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPOSIXAPIs Context triple: [Zephyr, supportsPOSIXAPIs, partial]
-
A.
supportsPositionIndependentCode
Indicates that one entity (such as a tool, platform, or environment) is capable of correctly handling or executing position-independent code generated by another.
-
B.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
C.
supportsPort
Indicates that one entity is capable of handling, providing, or being compatible with a specified port or port configuration.
-
D.
supportsRegionalFileSystems
Indicates that an entity provides compatibility with or functionality for file systems specific to particular regions or locales.
-
E.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a00d76d0e0881908d83a8dcce511167 |
completed | May 10, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a00d711805881909a94cfd1f25fb331 |
completed | May 10, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a00d76bde6c81909e564ab9cb0325af |
completed | May 10, 2026, 7:07 p.m. |
Created at: April 28, 2026, 4:16 a.m.