Triple
T19700878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welcome (ship) |
E473090
|
entity |
| Predicate | notablePassengerGroup |
P99024
|
FINISHED |
| Object | Quaker settlers |
—
|
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: Quaker settlers | Statement: [Welcome (ship), notablePassengerGroup, Quaker settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePassengerGroup Context triple: [Welcome (ship), notablePassengerGroup, Quaker settlers]
-
A.
primaryPassengerGroup
chosen
Indicates the main group of passengers that is most directly associated with or served by a given entity or context.
-
B.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
C.
notableChildrenGroup
Indicates that an entity has a group of children who are notable or significant in some recognized way.
-
D.
hasThroughPassengersWith
Indicates that two transportation segments, services, or locations are connected by passengers who travel through them without starting or ending their journey there.
-
E.
notableCharacterGroup
Indicates that a group of characters is especially prominent, significant, or noteworthy within a given context or work.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b4e01081908f857f219d5d7a24 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.