Triple
T27671923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pilgrims |
E697684
|
entity |
| Predicate | associatedWithMottoOrIdentity |
P176275
|
FINISHED |
| Object | club from a naval and maritime city |
—
|
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: club from a naval and maritime city | Statement: [The Pilgrims, associatedWithMottoOrIdentity, club from a naval and maritime city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMottoOrIdentity Context triple: [The Pilgrims, associatedWithMottoOrIdentity, club from a naval and maritime city]
-
A.
hasMottoOrAssociation
chosen
Indicates a relationship where an entity is linked to a motto, slogan, or associated phrase that represents or characterizes it.
-
B.
relatedToMotto
Indicates that one entity has an association or connection with a motto, such as embodying, expressing, or being defined by that motto.
-
C.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
D.
mottoLinked
Indicates that a motto is associated with or linked to a particular entity.
-
E.
sharesMottoWith
Indicates that two entities use or are associated with the same motto.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
Created at: April 27, 2026, 2:41 p.m.