Triple
T25285548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzie |
E633927
|
entity |
| Predicate | worksRemotelyWith |
P398
|
FINISHED |
| Object | Dustin Henderson |
—
|
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: Dustin Henderson | Statement: [Suzie, worksRemotelyWith, Dustin Henderson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksRemotelyWith Context triple: [Suzie, worksRemotelyWith, Dustin Henderson]
-
A.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
B.
mayWorkIn
Indicates that an entity is allowed or has the possibility to work in a particular place, organization, or context.
-
C.
worksWith
chosen
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
D.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
E.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:19 p.m.