Triple
T25980993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arawa |
E646068
|
entity |
| Predicate | associatedWithMine |
P73907
|
FINISHED |
| Object | Panguna mine |
—
|
NE NERFINISHED |
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: Panguna mine | Statement: [Arawa, associatedWithMine, Panguna mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMine Context triple: [Arawa, associatedWithMine, Panguna mine]
-
A.
associatedMine
chosen
Indicates that one entity is linked or connected to a particular mine, typically as its source, location, or relevant mining site.
-
B.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
C.
associatedWithCustom
Indicates a relationship where one entity is linked to or connected with another entity in a non-standard, user-defined, or customized manner.
-
D.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
E.
associatedWithBlock
Indicates a relationship where an entity is linked or connected to a specific block, typically as part of its context, structure, or grouping.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 22, 2026, 8:54 a.m.