Triple
T27733784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.ValueTuple |
E697486
|
entity |
| Predicate | supportsItemAccessByPosition |
P201030
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [System.ValueTuple, supportsItemAccessByPosition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsItemAccessByPosition Context triple: [System.ValueTuple, supportsItemAccessByPosition, true]
-
A.
supportsPosition
Indicates that one entity endorses, upholds, or provides backing for the stance, viewpoint, or role represented by another entity.
-
B.
providedForPosition
Indicates that something (such as a resource, benefit, or support) is supplied or made available specifically for a given role or position.
-
C.
hasPositionsFor
Indicates that one entity offers or contains available roles, jobs, or positions for another entity.
-
D.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
-
E.
hasPositioning
Indicates that one entity occupies, is arranged in, or is assigned a specific spatial or relative position with respect to another entity or reference frame.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
| PDg | Predicate description generation | batch_69ffc3eed97c819085c06ffe3699ff38 |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 27, 2026, 3:12 p.m.