Triple
T36872536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | typing.FrozenSet |
E911259
|
entity |
| Predicate | isSubscriptable |
P186734
|
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, isSubscriptable, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubscriptable Context triple: [typing.FrozenSet, isSubscriptable, True]
-
A.
requiresSubscript
Indicates that one element must be written with a subscript in relation to another element for proper notation or interpretation.
-
B.
isTabulatedBy
Indicates that data, values, or information are organized, arranged, or recorded in a table by a specified agent or process.
-
C.
hasSubproperty
Indicates that one property is a more specific version of another property, inheriting its meaning and constraints.
-
D.
isInterpretableIn
Indicates that one formal system, language, or theory can be meaningfully represented, understood, or given a semantics within another system, language, or theory.
-
E.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
- 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_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.