Triple
T23466880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GEO DataSets |
E569121
|
entity |
| Predicate | hasIdentifierPattern |
P8151
|
FINISHED |
| Object | GDSnnnnn |
—
|
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: GDSnnnnn | Statement: [GEO DataSets, hasIdentifierPattern, GDSnnnnn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdentifierPattern Context triple: [GEO DataSets, hasIdentifierPattern, GDSnnnnn]
-
A.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
B.
haveIdentifier
Indicates that an entity is associated with a specific identifier used to uniquely reference or distinguish it.
-
C.
hasRouteIdentifier
Indicates that an entity is associated with a specific route code or identifier used to distinguish it from other routes.
-
D.
hasStartPattern
Indicates that something begins with, or is characterized at its outset by, a specified pattern.
-
E.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6fc35c48190a67614fb4170f15b |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.