Triple
T8648232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Imperial Force |
E205032
|
entity |
| Predicate | servedOverseas |
P84123
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Australian Imperial Force, servedOverseas, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedOverseas Context triple: [Australian Imperial Force, servedOverseas, true]
-
A.
couldServeOverseas
Indicates that an entity has the ability or eligibility to perform service or duties in a foreign or overseas location.
-
B.
hasCountryServed
Indicates that a person or organization has provided service to, or performed duties on behalf of, a specified country.
-
C.
hasOverseasPresenceIn
Indicates that an entity maintains operations, offices, or activities in a foreign country or region.
-
D.
servesCountryGroup
Indicates that an entity provides service, support, or functions on behalf of a specified group of countries.
-
E.
locatedInOverseasCountry
Indicates that an entity is situated in a country that is overseas relative to a given reference location or jurisdiction.
- F. None of above. chosen
Provenance (4 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4812b7bc8190acb40da57cad293a |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc473e44988190a3b02498e5fff668 |
completed | March 31, 2026, 10:14 p.m. |
Created at: March 30, 2026, 6:29 p.m.