Triple
T306388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Public Engagement |
E6311
|
entity |
| Predicate | typeOfLiaison |
P5518
|
FINISHED |
| Object | public liaison |
—
|
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: public liaison | Statement: [Office of Public Engagement, typeOfLiaison, public liaison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLiaison Context triple: [Office of Public Engagement, typeOfLiaison, public liaison]
-
A.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
B.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
typeOfDiplomaticRole
Indicates the specific kind or category of diplomatic position or function that an entity holds in relation to another.
-
D.
typeOfTrust
Indicates the specific kind or category of trust that characterizes the relationship between entities.
-
E.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.