Triple
T27866843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Net.CookieCollection |
E704378
|
entity |
| Predicate | indexer |
P163239
|
FINISHED |
| Object | Cookie this[string name] |
—
|
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: Cookie this[string name] | Statement: [System.Net.CookieCollection, indexer, Cookie this[string name]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexer Context triple: [System.Net.CookieCollection, indexer, Cookie this[string name]]
-
A.
indexer
Indicates a relationship where one entity organizes, catalogs, or creates an index for another entity’s contents or elements.
-
B.
indexingService
Indicates a service that organizes, catalogs, and maintains an index of items or data so they can be efficiently searched and retrieved.
-
C.
indexed
Indicates that one entity is organized, recorded, or referenced within a systematic index or catalog relative to another entity.
-
D.
coreIndex
Indicates the position or identifier of an entity within a central or primary ordered structure (its core sequence or index).
-
E.
canIndex
Indicates that one entity has the capability or permission to create, maintain, or use an index over another entity (such as data, documents, or resources) for efficient access or retrieval.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 6:21 p.m.