Triple
T28619493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FXC compiler |
E724344
|
entity |
| Predicate | supportsPreprocessing |
P203
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [FXC compiler, supportsPreprocessing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPreprocessing Context triple: [FXC compiler, supportsPreprocessing, yes]
-
A.
supportsPreprocessorIntegration
Indicates that one entity provides compatibility or mechanisms for integrating and working with a specified preprocessor.
-
B.
supportsProcesses
Indicates that one entity provides the necessary functionality, resources, or environment for certain processes of another entity to operate or be carried out.
-
C.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
supportsExceptionProcessing
Indicates that one entity provides the capability or mechanism for another entity to handle or process exceptions.
-
E.
allowsPremiumProcessing
Indicates that one entity permits another entity to use an expedited or premium processing service for a given request or operation.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a018f9c7cf88190adc5daf3806f2077 |
completed | May 11, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_6a018ca4e0e481908091f0c1f8a4c31b |
completed | May 11, 2026, 8 a.m. |
Created at: April 28, 2026, 4:32 a.m.