Triple
T36796721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lens Explorer |
E909202
|
entity |
| Predicate | hasDiscoveryRole |
P94584
|
FINISHED |
| Object | expands access to AR Lenses |
—
|
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: expands access to AR Lenses | Statement: [Lens Explorer, hasDiscoveryRole, expands access to AR Lenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscoveryRole Context triple: [Lens Explorer, hasDiscoveryRole, expands access to AR Lenses]
-
A.
hasDetectionRole
Indicates that one entity serves in a detection-related role or function with respect to another entity or process.
-
B.
hasFrontierRole
Indicates that an entity holds a designated role or function at the frontier or boundary of a system, domain, or organization.
-
C.
discovererRole
chosen
Indicates the role or capacity in which an entity participates as the discoverer of something.
-
D.
hasDisciplineRole
Indicates that an entity holds a specific role or function within a particular discipline or field.
-
E.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:12 p.m.