Triple
T36359402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M3071 |
E895445
|
entity |
| Predicate | hasModelIdentifierFormat |
P90216
|
FINISHED |
| Object | Apple model number |
—
|
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: Apple model number | Statement: [M3071, hasModelIdentifierFormat, Apple model number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModelIdentifierFormat Context triple: [M3071, hasModelIdentifierFormat, Apple model number]
-
A.
hasModelNumberPattern
chosen
Indicates that an entity’s model number follows or matches a specified pattern or format.
-
B.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
C.
hasConfigurationFormat
Indicates that an entity uses or is associated with a specific configuration format for its settings or parameters.
-
D.
identificationNumberFormat
Indicates the specific structural pattern or rules that an identification number must follow.
-
E.
hasFormatSpecification
Indicates that something is associated with a particular format definition or specification that describes how it should be structured or represented.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:09 p.m.