Triple
T6154455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bengoshi |
E137283
|
entity |
| Predicate | canWorkAt |
P41675
|
FINISHED |
| Object | law firms |
—
|
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: law firms | Statement: [bengoshi, canWorkAt, law firms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canWorkAt Context triple: [bengoshi, canWorkAt, law firms]
-
A.
mayWorkIn
chosen
Indicates that an entity is allowed or has the possibility to work in a particular place, organization, or context.
-
B.
canHire
Indicates that one entity has the authority or ability to employ or recruit another entity.
-
C.
eligibleWork
Indicates that a particular work satisfies the necessary conditions or criteria to qualify for a specified status, benefit, or consideration.
-
D.
ownsWork
Indicates that one entity has legal ownership or proprietary rights over a particular work or creation.
-
E.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d01ddb0819085b5f5338b86a25d |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.