Triple
T27856652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Postmaster General |
E704105
|
entity |
| Predicate | heldJointly |
P134392
|
FINISHED |
| Object | two office holders |
—
|
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: two office holders | Statement: [Joint Postmaster General, heldJointly, two office holders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldJointly Context triple: [Joint Postmaster General, heldJointly, two office holders]
-
A.
heldTogetherWith
Indicates that two or more entities are physically joined or kept in contact by some binding, fastening, or cohesive force.
-
B.
actedTogetherWith
Indicates that two entities participated in the same performance or production, collaborating or appearing together in an acting context.
-
C.
isHeldInConjunctionWith
chosen
Indicates that one event, activity, or occurrence takes place together with another at the same time or as part of a combined arrangement.
-
D.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
E.
formedTogetherWith
Indicates that two or more entities were created, established, or brought into existence at the same time or as part of the same formation process.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6390996cc8190b64aa747cc41bdcc |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:14 p.m.