Triple
T11344200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lane Pryce |
E268675
|
entity |
| Predicate | joinsCompanyAs |
P4325
|
FINISHED |
| Object | representative of Putnam, Powell & Lowe |
—
|
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: representative of Putnam, Powell & Lowe | Statement: [Lane Pryce, joinsCompanyAs, representative of Putnam, Powell & Lowe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinsCompanyAs Context triple: [Lane Pryce, joinsCompanyAs, representative of Putnam, Powell & Lowe]
-
A.
workedAs
chosen
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
B.
recruitedAs
Indicates that one entity has been brought into a role, position, or organization by another through a recruitment process.
-
C.
workAt
Indicates that an entity is employed by or performs work for a particular organization, company, or place.
-
D.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
E.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e6f8aeb4819080476f16a69b2ee3 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.