Triple
T36198013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Gregson |
E1047180
|
entity |
| Predicate | invitesToWork |
P25673
|
FINISHED |
| Object | Lady Edith Crawley |
—
|
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: Lady Edith Crawley | Statement: [Michael Gregson, invitesToWork, Lady Edith Crawley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invitesToWork Context triple: [Michael Gregson, invitesToWork, Lady Edith Crawley]
-
A.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
B.
coordinatesWorkOf
Indicates overseeing and organizing the tasks, efforts, or activities of others to ensure they work together effectively toward a common goal.
-
C.
appliedWork
Indicates that an entity has put effort, skill, or labor into performing or producing a particular work or task.
-
D.
invitesParticipationOf
chosen
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.