Triple
T26353271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bigadiç |
E662959
|
entity |
| Predicate | hasBoronReservesRank |
P6797
|
FINISHED |
| Object | among largest in the world |
—
|
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: among largest in the world | Statement: [Bigadiç, hasBoronReservesRank, among largest in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoronReservesRank Context triple: [Bigadiç, hasBoronReservesRank, among largest in the world]
-
A.
hasEstimatedNumberOfBunkers
Indicates that an entity is associated with an approximate or estimated count of bunkers.
-
B.
rankByReserveHoldings
chosen
Indicates an ordering of entities based on the size or value of their reserve holdings, typically from highest to lowest.
-
C.
isOneOfMainReservesOf
Indicates that an entity serves as one of the primary reserve sources or backup resources for another entity.
-
D.
hasCoalBasin
Indicates that one entity contains, includes, or is characterized by a coal-bearing geological basin associated with the other entity.
-
E.
isPrimaryReserveOf
Indicates that one entity serves as the main or principal reserve (backup or stored resource) for 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 26, 2026, 10:47 p.m.