Triple
T36771326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trient |
E908483
|
entity |
| Predicate | joinedCountryYear |
P64978
|
FINISHED |
| Object | 1919 |
—
|
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: 1919 | Statement: [Trient, joinedCountryYear, 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedCountryYear Context triple: [Trient, joinedCountryYear, 1919]
-
A.
joinedCountryOn
Indicates that an entity became a member of or formally entered a specific country on a particular date or at a specific time.
-
B.
rejoinedCountryYear
Indicates the year in which an entity re-entered or rejoined a particular country after having previously left or been separated from it.
-
C.
countryJoined
Indicates that a country became a member of, or formally entered into, a specific organization, union, alliance, or agreement.
-
D.
rejoinedCountry
Indicates that an entity has become part of a country again after having previously separated or left it.
-
E.
joinedInYear
chosen
Indicates that an entity became a member of, or started participating in, another entity (such as an organization, group, or institution) in a specified calendar year.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.