Triple
T26503565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Princess |
E669483
|
entity |
| Predicate | flagDuringService |
P19687
|
FINISHED |
| Object | Liberia |
—
|
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: Liberia | Statement: [Pacific Princess, flagDuringService, Liberia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagDuringService Context triple: [Pacific Princess, flagDuringService, Liberia]
-
A.
serviceDuring
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
-
B.
flagUsedBy
chosen
Indicates that a particular flag is officially used by a specified entity, such as a country, organization, or group.
-
C.
flagUsedIn
Indicates that a particular flag is employed or referenced within a given context, such as a program, configuration, or process.
-
D.
flagLater
Indicates that an item, event, or entity is marked to be reviewed, processed, or acted upon at a later time.
-
E.
primaryBaseDuringService
Indicates that a particular base or location serves as the main or designated primary base for an entity during a specified period of service.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6138baea48190b7c17200ea30aa7f |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:14 a.m.