Triple
T37172307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nortraship |
E920947
|
entity |
| Predicate | operatedInExile |
P89002
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nortraship, operatedInExile, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInExile Context triple: [Nortraship, operatedInExile, true]
-
A.
operatesInExile
chosen
Indicates that an entity continues its activities or functions while being formally based outside its home country or usual jurisdiction, typically due to displacement or political circumstances.
-
B.
exileOf
Indicates that one entity has been banished or forced to leave its home or native place, resulting in a state of exile associated with that entity.
-
C.
livedInExileIn
Indicates that an entity spent a period of time living outside its home country or usual place of residence due to exile, in a specified location.
-
D.
exiledWith
Indicates that two or more entities were banished or forced to leave a place together as part of the same exile.
-
E.
wasExiled
Indicates that an entity was forcibly sent away from their home or country, typically as a punishment or due to political or social pressures.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a020ab9630c8190a55efd5704cc6043 |
completed | May 11, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_6a020800e2b88190a1a37e710d8c92bf |
completed | May 11, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:15 p.m.