Triple
T32123533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSKeyedArchiver |
E820439
|
entity |
| Predicate | outputFormatOption |
P105363
|
FINISHED |
| Object | NSPropertyListBinaryFormat_v1_0 |
—
|
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: NSPropertyListBinaryFormat_v1_0 | Statement: [NSKeyedArchiver, outputFormatOption, NSPropertyListBinaryFormat_v1_0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputFormatOption Context triple: [NSKeyedArchiver, outputFormatOption, NSPropertyListBinaryFormat_v1_0]
-
A.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
-
B.
outputSpecifier
chosen
Indicates how the result or outcome of an action, process, or computation is to be formatted, structured, or delivered.
-
C.
decidingSetFormat
Indicates that an entity determines or specifies the format or structure in which a set is represented or organized.
-
D.
selectionFormat
Indicates the specific structure or style in which a selection or choice is represented or presented.
-
E.
outputConfiguration
Indicates how the results or data produced by a process, system, or component are structured, formatted, or directed to their destination.
- 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_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:29 a.m.