Triple
T28264021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google+ |
E712652
|
entity |
| Predicate | dataExportTool |
P60091
|
FINISHED |
| Object | Google Takeout |
—
|
NE NERFINISHED |
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: Google Takeout | Statement: [Google+, dataExportTool, Google Takeout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataExportTool Context triple: [Google+, dataExportTool, Google Takeout]
-
A.
dataExportOffered
chosen
Indicates that an entity makes data available for export to another party or system.
-
B.
dataAvailableAs
Indicates that specific data can be accessed or obtained in a particular form, format, or representation.
-
C.
historicalExport
Indicates that an entity was exported from one place to another during a past or historically significant period.
-
D.
talentExportTo
Indicates a relationship where talent (such as skilled individuals or expertise) is transferred or sent from one entity or location to another.
-
E.
supportsImportExport
Indicates that one entity provides functionality for importing and exporting data or resources to and from another entity.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6441c2ed081909128d8fe21b14fa4 |
completed | May 2, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:13 p.m.