Triple
T33397780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International GPS Service for Geodynamics |
E855215
|
entity |
| Predicate | productUsers |
P93351
|
FINISHED |
| Object | scientific community |
—
|
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: scientific community | Statement: [International GPS Service for Geodynamics, productUsers, scientific community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productUsers Context triple: [International GPS Service for Geodynamics, productUsers, scientific community]
-
A.
hasProductUser
chosen
Indicates that a product is associated with or used by a particular user.
-
B.
productsUsedIn
Indicates that certain products are utilized or applied within a particular process, context, or entity.
-
C.
usesProduct
Indicates that one entity makes use of, applies, or employs a particular product.
-
D.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
E.
byProduct
Indicates that one entity is produced incidentally or as a secondary result of a process, activity, or creation involving 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 1, 2026, 1:35 a.m.