Triple
T30710021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monmouth's rebel infantry |
E781864
|
entity |
| Predicate | notableLocationOfRecruitment |
P3858
|
FINISHED |
| Object | Somerset |
E59760
|
NE 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: Somerset | Statement: [Monmouth's rebel infantry, notableLocationOfRecruitment, Somerset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLocationOfRecruitment Context triple: [Monmouth's rebel infantry, notableLocationOfRecruitment, Somerset]
-
A.
recruitmentLocation
Indicates the place or geographic area where the recruitment or hiring of individuals occurs.
-
B.
notableLocation
chosen
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
C.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
D.
canBeRecruitedFrom
Indicates that one entity is eligible to be recruited, obtained, or enlisted starting from or via another specified entity or source.
-
E.
notableRecruit
Indicates that an entity is recognized as a significant or high-profile addition to an organization, group, or team.
- F. None of above.
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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28c7b3b254819097d00c24b4406863 |
completed | June 10, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:35 p.m.