Triple
T36559425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (1978) |
E901787
|
entity |
| Predicate | laterRegistry |
P202727
|
FINISHED |
| Object | Panama |
—
|
NE NERFINISHED |
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: Panama | Statement: [SS Empress of Britain (1978), laterRegistry, Panama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRegistry Context triple: [SS Empress of Britain (1978), laterRegistry, Panama]
-
A.
laterClass
Indicates that one class occurs or is scheduled at a time later than another class.
-
B.
laterConfiguration
Indicates that one configuration occurs after another in time, representing a subsequent or later state relative to a prior configuration.
-
C.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
D.
laterDetector
Indicates that one detector operates or is triggered at a later time than another detector in a given context.
-
E.
laterBase
Indicates that one event, state, or version occurs or is valid at a later time than another referenced event, state, or version.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00b03a50a88190bfb95cdcfc6142a2 |
completed | May 10, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_6a00afe55f248190b2cb4c7e62cc3ffc |
completed | May 10, 2026, 4:18 p.m. |
| PDg | Predicate description generation | batch_6a00b03991148190ad8017ec56dbde6c |
completed | May 10, 2026, 4:20 p.m. |
Created at: May 3, 2026, 4:11 p.m.