Triple
T32122971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSSecureCoding |
E820428
|
entity |
| Predicate | requiresPropertyType |
P42360
|
FINISHED |
| Object | BOOL |
—
|
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: BOOL | Statement: [NSSecureCoding, requiresPropertyType, BOOL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPropertyType Context triple: [NSSecureCoding, requiresPropertyType, BOOL]
-
A.
requiresProperty
chosen
Indicates that one entity depends on another entity possessing a specific property or attribute in order for a condition, action, or relationship to hold.
-
B.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
-
C.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
D.
propertiesType
Indicates that one entity is classified as a specific type or category of properties associated with another entity.
-
E.
inheritsPropertyType
Indicates that one entity derives or acquires its property type definition from another entity, typically following an inheritance or subtype relationship.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: May 1, 2026, 12:28 a.m.