Triple
T24950002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shot heard round the world |
E624301
|
entity |
| Predicate | originOfPhrase |
P142073
|
FINISHED |
| Object | poem "Concord Hymn" |
—
|
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: poem "Concord Hymn" | Statement: [Shot heard round the world, originOfPhrase, poem "Concord Hymn"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfPhrase Context triple: [Shot heard round the world, originOfPhrase, poem "Concord Hymn"]
-
A.
sourceOfPhrase
chosen
Indicates that one entity is the origin or provider of a particular phrase used or referenced by another entity.
-
B.
religiousPhraseOrigin
Indicates that one entity is the source, origin, or provenance of a particular religious phrase associated with another entity.
-
C.
meaningOfPhrase
Indicates that one entity expresses or defines the semantic content or interpretation of a given phrase.
-
D.
etymologicalSource
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
-
E.
historicalOriginMeaning
Indicates that one entity explains the original historical source or derivational meaning of another entity.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 18, 2026, 5:56 a.m.