Triple
T32848700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Nicholas Bascom |
E840179
|
entity |
| Predicate | hasNotableInteractionWith |
P85532
|
FINISHED |
| Object | Cochise |
—
|
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: Cochise | Statement: [George Nicholas Bascom, hasNotableInteractionWith, Cochise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableInteractionWith Context triple: [George Nicholas Bascom, hasNotableInteractionWith, Cochise]
-
A.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
B.
hasNotableImpressionOf
Indicates that one entity holds a particularly strong, memorable, or significant impression of another entity.
-
C.
hasNotableInterchange
Indicates that there exists a significant or well-known point of exchange, connection, or transfer between the related entities.
-
D.
hasNotableResponse
Indicates that an entity has received a significant, noteworthy, or widely recognized reaction or feedback in response to it.
-
E.
notablePropInteraction
chosen
Indicates a significant or noteworthy interaction or relationship occurring between the specified entities.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0154b16a3c8190b808a460ae3a91ac |
completed | May 11, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a01539f19d88190b2de63f5262b1074 |
completed | May 11, 2026, 3:57 a.m. |
Created at: May 1, 2026, 1:17 a.m.