Triple
T28019745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauge 1 |
E707652
|
entity |
| Predicate | allowsFeature |
P203
|
FINISHED |
| Object | working couplers |
—
|
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: working couplers | Statement: [Gauge 1, allowsFeature, working couplers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsFeature Context triple: [Gauge 1, allowsFeature, working couplers]
-
A.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
C.
accessFeature
Indicates that one entity is permitted to use or interact with a specific feature or capability of another entity.
-
D.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
E.
passesFeature
Indicates that one entity successfully satisfies, verifies, or meets the criteria of a specified feature or test condition associated with 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 8:09 p.m.