Triple
T576869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Maps |
E13774
|
entity |
| Predicate | usesDataSource |
P11520
|
FINISHED |
| Object | satellite data |
—
|
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: satellite data | Statement: [Google Maps, usesDataSource, satellite data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDataSource Context triple: [Google Maps, usesDataSource, satellite data]
-
A.
usedDataFrom
chosen
Indicates that one entity utilized or relied on data originating from another entity.
-
B.
usesAccessMethod
Indicates that one entity employs or relies on a particular access method to reach, interact with, or retrieve another entity or resource.
-
C.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
D.
usesSamplingOf
Indicates that one entity employs or relies on a sample or subset derived from another entity for its operation, analysis, or processing.
-
E.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b68cc808190b1ba45bdad78443d |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.