Triple
T5016161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Sharing |
E112744
|
entity |
| Predicate | maintainsSeparateRecommendations |
P61541
|
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, maintainsSeparateRecommendations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsSeparateRecommendations Context triple: [Family Sharing, maintainsSeparateRecommendations, true]
-
A.
numberOfRecommendations
Indicates the quantity of recommendations associated with or given to a particular entity or item.
-
B.
implementsRecommendationOf
Indicates that one entity carries out or puts into practice a recommendation that was proposed or issued by another entity.
-
C.
submitsRecommendationsTo
Indicates that one entity formally sends or presents recommendations to another entity for consideration or action.
-
D.
natureOfRecommendations
Indicates the type, basis, or characteristics of the recommendations being provided in a given context.
-
E.
commendedFor
Indicates that one entity has expressed praise or approval toward another entity specifically because of a particular action, quality, or achievement.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:35 p.m.