Triple
T25388817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Hiram Combs |
E631598
|
entity |
| Predicate | influencedPlaceName |
P99755
|
FINISHED |
| Object | Combs, Arkansas |
—
|
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: Combs, Arkansas | Statement: [Captain Hiram Combs, influencedPlaceName, Combs, Arkansas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedPlaceName Context triple: [Captain Hiram Combs, influencedPlaceName, Combs, Arkansas]
-
A.
placeOfInfluence
Indicates the location or area where an entity exerts significant impact, authority, or cultural, social, or intellectual influence.
-
B.
inspiredByPlace
Indicates that something (such as a work, idea, or creation) originates from or is significantly influenced by a particular location or environment.
-
C.
cityOfInfluence
Indicates the city that significantly shapes, impacts, or exerts influence over a given entity.
-
D.
hasPlaceNamesakeIn
chosen
Indicates that something is named after a particular place or location.
-
E.
locationGaveRiseTo
Indicates that a particular location is the origin or source from which something (such as an event, movement, phenomenon, or entity) emerged or developed.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 1:47 p.m.