Triple
T23797641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhino |
E588580
|
entity |
| Predicate | suitProperties |
P153596
|
FINISHED |
| Object | nearly indestructible |
—
|
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: nearly indestructible | Statement: [Rhino, suitProperties, nearly indestructible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suitProperties Context triple: [Rhino, suitProperties, nearly indestructible]
-
A.
suitType
Indicates the specific category or style of suit associated with an entity (e.g., business suit, spacesuit, wetsuit).
-
B.
suit
Indicates that one entity is appropriate, fitting, or satisfactory for another entity or a particular purpose or situation.
-
C.
suitColor
Indicates that one entity has or is associated with a particular color of suit.
-
D.
hasSuit
Indicates that an entity possesses, wears, or is associated with a particular suit (such as clothing, armor, or a formal outfit).
-
E.
spanCharacteristic
Indicates that one entity has a particular measurable or descriptive property that characterizes the extent, duration, or range of another entity or phenomenon.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:50 p.m.