Triple
T2399143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of Cameroon in Washington, D.C. |
E47722
|
entity |
| Predicate | phoneCountryCode |
P247
|
FINISHED |
| Object | +1 |
—
|
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: +1 | Statement: [Embassy of Cameroon in Washington, D.C., phoneCountryCode, +1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phoneCountryCode Context triple: [Embassy of Cameroon in Washington, D.C., phoneCountryCode, +1]
-
A.
callingCode
chosen
Indicates the telephone country or area code associated with an entity for making phone calls.
-
B.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
C.
areaCode
Indicates that a location, phone number, or region is associated with a specific telephone area code.
-
D.
telephoneStandard
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
-
E.
FIPSCountryCode
Indicates that an entity is associated with a specific country as identified by its FIPS (Federal Information Processing Standards) country code.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc8c798248190a41bb08d9148f009 |
completed | March 7, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.