Triple
T32656057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish consulate |
E834865
|
entity |
| Predicate | permanentStaff |
P50783
|
FINISHED |
| Object | Irish diplomats |
—
|
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: Irish diplomats | Statement: [Irish consulate, permanentStaff, Irish diplomats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentStaff Context triple: [Irish consulate, permanentStaff, Irish diplomats]
-
A.
permanentPosition
Indicates that an entity holds a long-term, ongoing role or job with another entity, without a predefined end date.
-
B.
isPermanentOffice
Indicates that an office or position is established on a lasting, ongoing basis rather than being temporary or time-limited.
-
C.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
D.
personnel
chosen
Indicates that an entity serves as staff or workforce associated with another entity, such as an organization, project, or facility.
-
E.
employedSystem
Indicates that a system is used or operated in the context of an employment or work-related arrangement.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c77b504c8190aa225fad8f2cb2aa |
completed | May 3, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:08 a.m.