Triple
T8967064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Encounter Beach |
E214163
|
entity |
| Predicate | hasNotableEventParticipants |
P6467
|
FINISHED |
| Object | Pilgrims |
—
|
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: Pilgrims | Statement: [First Encounter Beach, hasNotableEventParticipants, Pilgrims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEventParticipants Context triple: [First Encounter Beach, hasNotableEventParticipants, Pilgrims]
-
A.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
B.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
C.
notableParticipant
chosen
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
-
D.
hasCoSanctionedEventsWith
Indicates that two entities have jointly sanctioned or approved the same events.
-
E.
hasCoSanctionedEventWith
Indicates that two or more entities have jointly imposed or participated in the same sanction-related event or action.
- 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc676389948190aa78fdf6a5ae74a5 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:01 p.m.