Triple
T30299928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSArray |
E770627
|
entity |
| Predicate | supportsFastEnumeration |
P207224
|
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: [NSArray, supportsFastEnumeration, YES]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFastEnumeration Context triple: [NSArray, supportsFastEnumeration, YES]
-
A.
containsFast
Indicates that one entity includes or holds another entity in a way that allows rapid or high-speed access, interaction, or processing.
-
B.
hasFast
Indicates that an entity possesses or is associated with something characterized by high speed or quickness.
-
C.
isRandomAccess
Indicates that the target can be accessed directly at arbitrary positions without needing to traverse preceding elements sequentially.
-
D.
supportsSequentialAccessFiles
Indicates that the subject provides or is compatible with files that are accessed sequentially rather than randomly.
-
E.
hasFastLines
Indicates that the subject possesses or is associated with lines that operate or move at a high speed.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 7:48 p.m.