Triple
T32443913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian expedition |
E829090
|
entity |
| Predicate | nationalityOfTeamMembers |
P38099
|
FINISHED |
| Object | Austrian |
—
|
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: Austrian | Statement: [Austrian expedition, nationalityOfTeamMembers, Austrian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalityOfTeamMembers Context triple: [Austrian expedition, nationalityOfTeamMembers, Austrian]
-
A.
countryOfTeam
chosen
Indicates that a team is associated with or represents a particular country.
-
B.
countryMembers
Indicates that certain entities are members or constituent parts of a specified country.
-
C.
homeCountryTeamOf
Indicates that one entity is the national team representing the home country of another entity.
-
D.
memberNation
Indicates that one entity is a nation that belongs to, or holds membership in, an international organization or group represented by the other entity.
-
E.
nationalTeamFor
Indicates that one entity serves as the national team representing another entity, typically a country or nation, in a given sport or activity.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 12:55 a.m.