Triple
T14826193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambing Flat |
E348577
|
entity |
| Predicate | hasConflictCause |
P115981
|
FINISHED |
| Object | competition over gold claims |
—
|
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: competition over gold claims | Statement: [Lambing Flat, hasConflictCause, competition over gold claims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConflictCause Context triple: [Lambing Flat, hasConflictCause, competition over gold claims]
-
A.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
B.
hasRelatedConflict
Indicates that one entity is associated with another entity through a related or connected conflict, dispute, or incompatibility.
-
C.
hasPrimaryConflictType
Indicates that an entity is associated with its main or most significant type of conflict among possible conflict categories.
-
D.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
E.
triggersConflict
Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
- F. None of above. chosen
Provenance (4 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0713700819097bbb0352650984b |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90806f3881908fcbfec5bd4ab4d2 |
completed | April 14, 2026, 7:07 p.m. |
Created at: April 10, 2026, 1:51 a.m.