Triple
T35198986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Memphis |
E1016343
|
entity |
| Predicate | isTrustedBy |
P127947
|
FINISHED |
| Object | Bob Lee Swagger |
—
|
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: Bob Lee Swagger | Statement: [Nick Memphis, isTrustedBy, Bob Lee Swagger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTrustedBy Context triple: [Nick Memphis, isTrustedBy, Bob Lee Swagger]
-
A.
hasTrust
Indicates that one entity has confidence in the reliability, integrity, or good intentions of another entity.
-
B.
trustedStatus
chosen
Indicates that one entity regards another as reliable, dependable, or worthy of confidence in a given context.
-
C.
providedCrossSignedTrustFor
Indicates that one entity has established mutual, reciprocal trust with another by cross-signing each other’s credentials or trust assertions.
-
D.
trustModel
Indicates that one entity relies on or has confidence in the reliability, integrity, or performance of another entity or system.
-
E.
trustAnchoredVia
Indicates that a relationship of trust is established or justified through a specific intermediary or anchoring mechanism (such as a trusted authority, key, or certificate).
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78e331ab08190966ad7ec0ec8d846 |
completed | May 3, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.