Triple
T5016146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Sharing |
E112744
|
entity |
| Predicate | allowsFindMyDeviceSharing |
P42910
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Family Sharing, allowsFindMyDeviceSharing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsFindMyDeviceSharing Context triple: [Family Sharing, allowsFindMyDeviceSharing, true]
-
A.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
-
B.
supportsShares
Indicates that one entity provides assistance, endorsement, or resources to another entity in the context of shared ownership, shared resources, or jointly held interests.
-
C.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
D.
supportsDeviceManagement
chosen
Indicates that one entity provides capabilities or functionality to manage, configure, or control another entity’s devices.
-
E.
canBeAirDropped
Indicates that an item or entity is suitable to be delivered or deployed by being dropped from an aircraft.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732f4c5c8190b90f8e4daab458ee |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.