Triple
T25270270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chefoo |
E633548
|
entity |
| Predicate | hasForeignPresence |
P14426
|
FINISHED |
| Object | foreign consulates |
—
|
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: foreign consulates | Statement: [Chefoo, hasForeignPresence, foreign consulates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasForeignPresence Context triple: [Chefoo, hasForeignPresence, foreign consulates]
-
A.
hasForeignPolicy
Indicates that an entity defines, follows, or is associated with a particular foreign policy in its relations with other entities or states.
-
B.
hasForeignRepresentation
Indicates that an entity maintains an official representative or representation in a foreign country or external jurisdiction.
-
C.
hasOverseasPresenceIn
chosen
Indicates that an entity maintains operations, offices, or activities in a foreign country or region.
-
D.
fieldPresenceIn
Indicates that something exists or is located within a particular field, area, or domain.
-
E.
hasLargePresenceIn
Indicates that an entity maintains a significant or dominant level of activity, influence, or representation within a specified location, domain, or context.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 1:16 p.m.