Triple
T36872555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | typing.FrozenSet |
E911259
|
entity |
| Predicate | isHashableCollection |
P186623
|
FINISHED |
| Object | True |
—
|
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: True | Statement: [typing.FrozenSet, isHashableCollection, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHashableCollection Context triple: [typing.FrozenSet, isHashableCollection, True]
-
A.
requiresHashableElements
Indicates that the relationship or operation can only be applied when all involved elements support hashing (i.e., can be used as keys in hash-based structures).
-
B.
isCollectionOf
Indicates that one entity is a group or aggregate composed of multiple instances or elements of another entity.
-
C.
isCollection
Indicates that an entity functions as a collection that groups or aggregates multiple items or elements.
-
D.
isPermanentCollectionOf
Indicates that one entity serves as the enduring, officially retained collection to which another entity permanently belongs.
-
E.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.