Triple
T9027830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | App Clips |
E216090
|
entity |
| Predicate | canShareDataWith |
P77966
|
FINISHED |
| Object | corresponding full app (via shared container) |
—
|
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: corresponding full app (via shared container) | Statement: [App Clips, canShareDataWith, corresponding full app (via shared container)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canShareDataWith Context triple: [App Clips, canShareDataWith, corresponding full app (via shared container)]
-
A.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
-
B.
allowsLocationSharing
Indicates that one entity permits another entity to share its location information.
-
C.
sharesUSRightsWith
Indicates that one entity holds and grants to another entity shared rights or interests specifically related to the United States.
-
D.
dataSharedWith
chosen
Indicates that some data has been disclosed or made accessible by one entity to another entity.
-
E.
allowsAppleFitnessPlusSharing
Indicates that an entity permits Apple Fitness+ subscription access to be shared with other eligible users.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7fcb308190af90d6be8700e498 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.