Triple
T23797643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhino |
E588580
|
entity |
| Predicate | suitEnhancement |
P39508
|
FINISHED |
| Object | augments physical strength |
—
|
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: augments physical strength | Statement: [Rhino, suitEnhancement, augments physical strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suitEnhancement Context triple: [Rhino, suitEnhancement, augments physical strength]
-
A.
suit
Indicates that one entity is appropriate, fitting, or satisfactory for another entity or a particular purpose or situation.
-
B.
suitType
Indicates the specific category or style of suit associated with an entity (e.g., business suit, spacesuit, wetsuit).
-
C.
comfortUpgrade
Indicates an enhancement made to increase the physical or emotional comfort associated with an entity or experience.
-
D.
adjustsFor
Indicates that one entity modifies, compensates, or accounts for the effects of another entity to achieve a corrected or normalized result.
-
E.
enhancedBy
chosen
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6dea2888190b3ff1c96da5cfefb |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:50 p.m.