Triple
T33963652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (2002) |
E870789
|
entity |
| Predicate | hasLaunchCentury |
P191522
|
FINISHED |
| Object | 21st century |
—
|
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: 21st century | Statement: [SS Empress of Britain (2002), hasLaunchCentury, 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchCentury Context triple: [SS Empress of Britain (2002), hasLaunchCentury, 21st century]
-
A.
implementedInCentury
chosen
Indicates that an entity (such as a work, system, or concept) was created, developed, or put into effect during a specified century.
-
B.
coveredSinceCentury
Indicates that one entity has been covered, coated, or kept under coverage continuously starting from a specified century.
-
C.
claimedInCentury
Indicates that a claim or assertion was made or recorded during a specified century.
-
D.
developedSinceCentury
Indicates that something began to be developed or came into existence starting from a specified century onward.
-
E.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: May 1, 2026, 1:50 a.m.