Triple
T8408461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Sheets API |
E198560
|
entity |
| Predicate | usesResourceIdentifier |
P3732
|
FINISHED |
| Object | spreadsheetId |
—
|
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: spreadsheetId | Statement: [Google Sheets API, usesResourceIdentifier, spreadsheetId]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesResourceIdentifier Context triple: [Google Sheets API, usesResourceIdentifier, spreadsheetId]
-
A.
usedResource
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
-
B.
usesResourceSeparation
Indicates that one entity applies or enforces a separation of resources between entities or processes, preventing them from sharing or interfering with each other’s resources.
-
C.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
isResourceFor
Indicates that one entity serves as a resource, support, or means of use for another entity.
-
E.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
- 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb8315a8a8819097f6da11b909b527 |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.