Triple
T3273378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samothrace |
E68701
|
entity |
| Predicate | rejoinedCountryYear |
P47035
|
FINISHED |
| Object | 1913 |
—
|
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: 1913 | Statement: [Samothrace, rejoinedCountryYear, 1913]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejoinedCountryYear Context triple: [Samothrace, rejoinedCountryYear, 1913]
-
A.
reestablishedInYear
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
B.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
C.
countryJoined
Indicates that a country became a member of, or formally entered into, a specific organization, union, alliance, or agreement.
-
D.
countryAfterSuccession
Indicates that one country is the successor state that takes over from another country after a political or territorial succession.
-
E.
reunificationStatus
Indicates the current state or outcome of efforts to bring previously separated entities back together into a single unified whole.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff74af88190809313743b439ff0 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.