Triple
T6263580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let My People Go movement |
E140357
|
entity |
| Predicate | sloganDerivedFrom |
P30365
|
FINISHED |
| Object | Biblical phrase "Let my people go" |
—
|
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: Biblical phrase "Let my people go" | Statement: [Let My People Go movement, sloganDerivedFrom, Biblical phrase "Let my people go"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sloganDerivedFrom Context triple: [Let My People Go movement, sloganDerivedFrom, Biblical phrase "Let my people go"]
-
A.
sloganGivenBy
Indicates that a particular slogan is provided, coined, or assigned by a specific entity.
-
B.
sloganUsedIn
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
-
C.
mottoDerivedFrom
chosen
Indicates that one motto is derived, adapted, or taken from another source, such as a phrase, text, or earlier motto.
-
D.
associatedWithFamousSlogan
Indicates that an entity is connected to, known for, or commonly linked with a particular famous slogan.
-
E.
sloganCategory
Indicates that a slogan is classified as belonging to a particular category or type.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06387fec0819095b47a37b9402aa9 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.