Triple
T17621663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Gunn |
E429721
|
entity |
| Predicate | roleAtWolframAndHart |
P128313
|
FINISHED |
| Object | head of legal operations for Angel’s team |
—
|
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: head of legal operations for Angel’s team | Statement: [Charles Gunn, roleAtWolframAndHart, head of legal operations for Angel’s team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtWolframAndHart Context triple: [Charles Gunn, roleAtWolframAndHart, head of legal operations for Angel’s team]
-
A.
roleInWatchmen
Indicates that one entity has a specific role or function within the context of the work "Watchmen" in relation to the other entity.
-
B.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
-
C.
CorwinRole
Indicates that an entity holds or is assigned a specific role or function in relation to Corwin.
-
D.
roleInCreed
Indicates that an entity holds a specific role or function within a particular creed, doctrine, or belief system.
-
E.
roleInBrethrenCourt
Indicates that an entity holds a specific position or function within the Brethren Court organization or council.
- F. None of above. chosen
Provenance (4 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46db98c54819088dadec9f6bcc559 |
completed | April 19, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:51 a.m.