Triple
T12086568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone 12 Pro Max |
E287819
|
entity |
| Predicate | lidarScanner |
P49003
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [iPhone 12 Pro Max, lidarScanner, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lidarScanner Context triple: [iPhone 12 Pro Max, lidarScanner, yes]
-
A.
groundControlStation
Indicates a relationship where an entity functions as or is associated with a ground-based control station that manages or communicates with another system or platform.
-
B.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
C.
scans
chosen
Indicates performing a systematic examination or inspection of something, often using a device or method to detect, read, or analyze its contents or structure.
-
D.
scanDirection
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
-
E.
sensorCoverage
Indicates that a sensor’s detection or monitoring area spatially covers or includes a given region, object, or point.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.