Triple
T163903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. embassies |
E2968
|
entity |
| Predicate | typicalServices |
P4690
|
FINISHED |
| Object | passport services for U.S. citizens |
—
|
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: passport services for U.S. citizens | Statement: [U.S. embassies, typicalServices, passport services for U.S. citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServices Context triple: [U.S. embassies, typicalServices, passport services for U.S. citizens]
-
A.
service
chosen
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
B.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
C.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
D.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
E.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2566392208190a538ea9aa1fac53e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.