Triple
T30759072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will Gardner |
E783176
|
entity |
| Predicate | roleAtFirm |
P120639
|
FINISHED |
| Object | managing partner |
—
|
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: managing partner | Statement: [Will Gardner, roleAtFirm, managing partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtFirm Context triple: [Will Gardner, roleAtFirm, managing partner]
-
A.
roleInFirm
chosen
Indicates the specific position, function, or responsibility an entity holds within a firm or organization.
-
B.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
-
C.
legalProfessionRole
Indicates that one entity holds or performs a specific professional role within the legal domain in relation to another entity or context.
-
D.
hasMemberFirm
Indicates that an organization includes another organization as one of its affiliated or constituent firms.
-
E.
legalCaseRole
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 8:39 p.m.