Triple
T35422568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tubular |
E1023832
|
entity |
| Predicate | requiresExtensiveUseOf |
P132991
|
FINISHED |
| Object | P-Balloon |
—
|
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: P-Balloon | Statement: [Tubular, requiresExtensiveUseOf, P-Balloon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresExtensiveUseOf Context triple: [Tubular, requiresExtensiveUseOf, P-Balloon]
-
A.
hasExtensive
Indicates that one entity possesses a large, wide-ranging, or comprehensive amount or degree of another entity or attribute.
-
B.
intensiveUse
chosen
Indicates a relationship where an entity is used in a concentrated, frequent, or high-intensity manner by another entity.
-
C.
isOftenRequiredFor
Indicates that one entity is frequently needed or commonly necessary for the occurrence, use, or success of another entity or activity.
-
D.
hasMinimalUseOf
Indicates that one entity employs or relies on another entity only to the smallest necessary extent.
-
E.
usageRequirement
Indicates the conditions or prerequisites that must be met for something to be used or applied.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:03 p.m.