Triple
T33841993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian embassies |
E867382
|
entity |
| Predicate | mayAlsoServe |
P6337
|
FINISHED |
| Object | multiple accredited countries |
—
|
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: multiple accredited countries | Statement: [Romanian embassies, mayAlsoServe, multiple accredited countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAlsoServe Context triple: [Romanian embassies, mayAlsoServe, multiple accredited countries]
-
A.
mayServe
Indicates that one entity is permitted or authorized to provide a service or function to another entity.
-
B.
mayServeAt
Indicates that one entity is permitted or authorized to perform service or duties at a specified location, organization, or context.
-
C.
mayServeOn
Indicates that one entity is permitted or eligible to serve on another entity, such as a group, body, or committee.
-
D.
alsoServes
chosen
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
-
E.
alsoServedBy
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7005069dc8190a8473c015571a4a0 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.