Triple
T22329817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigris expedition |
E551992
|
entity |
| Predicate | notableLeaderNationality |
P147774
|
FINISHED |
| Object | Norwegian |
—
|
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: Norwegian | Statement: [Tigris expedition, notableLeaderNationality, Norwegian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLeaderNationality Context triple: [Tigris expedition, notableLeaderNationality, Norwegian]
-
A.
notableMemberNationality
Indicates that the notable member of a group or organization has the specified nationality.
-
B.
notableLeaderUS
Indicates that the subject is a prominent or historically significant leader associated with the United States.
-
C.
notableFormerLeader
Indicates that the subject was once a leader of the object and is recognized as particularly significant or prominent in that former leadership role.
-
D.
notableLeaderInCommons
Indicates that a person is recognized as a prominent or distinguished leader within the House of Commons.
-
E.
notableNationality
Indicates that an entity is notably associated with a particular nationality, often by origin, citizenship, or cultural identity.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1576ab52c819087563cd778d6bc5e |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:43 p.m.