Triple
T27733782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.ValueTuple |
E697486
|
entity |
| Predicate | supportsDeconstruction |
P120119
|
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, supportsDeconstruction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeconstruction Context triple: [System.ValueTuple, supportsDeconstruction, true]
-
A.
decomposesIn
Indicates that one entity breaks down or separates into another entity or set of entities as its components or products.
-
B.
deconstructs
chosen
Indicates that one entity systematically takes apart, analyzes, or dismantles another entity or its structure into constituent elements.
-
C.
hasDecomposition
Indicates that something can be broken down or separated into constituent parts, components, or simpler elements.
-
D.
assumeDecomposition
Indicates that one entity takes for granted or posits a particular way of breaking another entity into constituent parts or components.
-
E.
decomposesAt
Indicates that one entity breaks down or disintegrates into parts, components, or simpler substances at a specific location, condition, or context.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: April 27, 2026, 3:12 p.m.