Triple
T31911970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massim |
E814710
|
entity |
| Predicate | hasValuableType |
P173786
|
FINISHED |
| Object | shell necklaces |
—
|
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: shell necklaces | Statement: [Massim, hasValuableType, shell necklaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasValuableType Context triple: [Massim, hasValuableType, shell necklaces]
-
A.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
B.
hasGoodType
Indicates that an entity possesses a type or classification considered appropriate, valid, or of high quality according to some defined criteria.
-
C.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasValue
Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:01 a.m.