Triple
T6372805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Singapore Air Force |
E143390
|
entity |
| Predicate | operatesAbroad |
P14426
|
FINISHED |
| Object | overseas training detachments |
—
|
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: overseas training detachments | Statement: [Republic of Singapore Air Force, operatesAbroad, overseas training detachments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesAbroad Context triple: [Republic of Singapore Air Force, operatesAbroad, overseas training detachments]
-
A.
operatesInternationally
Indicates that the entity conducts activities or business across national borders in multiple countries.
-
B.
operatesInCountries
Indicates that an entity conducts its activities or business within the specified countries.
-
C.
hasOverseasPresenceIn
chosen
Indicates that an entity maintains operations, offices, or activities in a foreign country or region.
-
D.
operatesToContinents
Indicates that an entity conducts or provides operations or services that extend across or are directed toward multiple continents.
-
E.
couldServeOverseas
Indicates that an entity has the ability or eligibility to perform service or duties in a foreign or overseas location.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06829d76c819092b476631459233a |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.