Triple
T9740829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sign in with Apple |
E236179
|
entity |
| Predicate | dataSharedWithApps |
P77966
|
FINISHED |
| Object | user name (optionally) |
—
|
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: user name (optionally) | Statement: [Sign in with Apple, dataSharedWithApps, user name (optionally)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataSharedWithApps Context triple: [Sign in with Apple, dataSharedWithApps, user name (optionally)]
-
A.
dataSharedWith
chosen
Indicates that some data has been disclosed or made accessible by one entity to another entity.
-
B.
sharesMembersWith
Indicates that two groups or collections have one or more members in common.
-
C.
homeGroundSharedWith
Indicates that two teams or organizations use the same venue or location as their home ground.
-
D.
sharesUSRightsWith
Indicates that one entity holds and grants to another entity shared rights or interests specifically related to the United States.
-
E.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f2af3e48190b83a442cd0e84062 |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.