Triple
T11958176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GAS |
E284603
|
entity |
| Predicate | supportsConditionalAssembly |
P17334
|
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: [GAS, supportsConditionalAssembly, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsConditionalAssembly Context triple: [GAS, supportsConditionalAssembly, yes]
-
A.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
B.
assemblyRequired
Indicates that the associated item or components must be put together or constructed before they can be used.
-
C.
hasAssemblyType
chosen
Indicates that an entity is associated with or classified by a specific type or method of assembly.
-
D.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
E.
supportsCondition
Indicates that one entity helps maintain, enable, or is compatible with a particular condition or state in another entity.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903681a00819098c2b5260e2ef834 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.