Triple
T27723665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beverly Mantle |
E699035
|
entity |
| Predicate | sharesProfessionalPracticeWith |
P116886
|
FINISHED |
| Object | Elliot Mantle |
—
|
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: Elliot Mantle | Statement: [Beverly Mantle, sharesProfessionalPracticeWith, Elliot Mantle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesProfessionalPracticeWith Context triple: [Beverly Mantle, sharesProfessionalPracticeWith, Elliot Mantle]
-
A.
sharesPracticesWith
chosen
Indicates that two entities engage in or follow similar methods, behaviors, or operational practices.
-
B.
sharesProfessionWith
Indicates that two entities have the same profession or occupational role.
-
C.
sharesWorkWith
Indicates that one entity collaborates or participates jointly in work or tasks with another entity.
-
D.
sharesCompetencesWith
Indicates that two entities possess and can apply the same or overlapping set of skills, abilities, or areas of expertise.
-
E.
partnerInProfession
Indicates that two or more entities share a professional partnership or collaborate together within the same occupation or field.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 27, 2026, 3:08 p.m.