Triple
T35753423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainmaster |
E1033375
|
entity |
| Predicate | indicatesAttribute |
P136535
|
FINISHED |
| Object | exceptional performance in rain |
—
|
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: exceptional performance in rain | Statement: [Rainmaster, indicatesAttribute, exceptional performance in rain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesAttribute Context triple: [Rainmaster, indicatesAttribute, exceptional performance in rain]
-
A.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
-
B.
holdsAttribute
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular attribute or property.
-
C.
conveysAttribute
Indicates that one entity communicates, expresses, or imparts a particular attribute or quality to another entity.
-
D.
attributeType
Indicates that one entity specifies the kind or category of attribute that characterizes another entity.
-
E.
isAttributeClass
Indicates that one entity functions as a defining attribute or characteristic class for 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a198e24881909cc292e420269a8c |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.