Triple
T18875896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Wells |
E461683
|
entity |
| Predicate | relationshipToJackTeller |
P125661
|
FINISHED |
| Object | reluctant mentor |
—
|
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: reluctant mentor | Statement: [Nick Wells, relationshipToJackTeller, reluctant mentor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToJackTeller Context triple: [Nick Wells, relationshipToJackTeller, reluctant mentor]
-
A.
relationshipToJack
chosen
Indicates the specific type of personal or social connection an entity has with Jack.
-
B.
financialRelationshipWith
Indicates a financial connection or association between entities, such as ownership, investment, funding, or other monetary ties.
-
C.
hasFinancialInstitution
Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
-
D.
relationshipToStandingOrders
Indicates the nature or status of an entity’s connection or applicability to existing standing orders.
-
E.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3ce07788190a179705eb1b6c824 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.