Triple
T4741021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Stadium (Baltimore) |
E105239
|
entity |
| Predicate | hasMemorialInscription |
P57501
|
FINISHED |
| Object | Time will not dim the glory of their deeds |
—
|
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: Time will not dim the glory of their deeds | Statement: [Memorial Stadium (Baltimore), hasMemorialInscription, Time will not dim the glory of their deeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemorialInscription Context triple: [Memorial Stadium (Baltimore), hasMemorialInscription, Time will not dim the glory of their deeds]
-
A.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
B.
hasGraveInscription
chosen
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
-
C.
hasNumberOfNamesInscribed
Indicates the quantity of distinct names that are inscribed on a given entity.
-
D.
hasCommemorativePlaques
Indicates that one entity possesses or displays commemorative plaques associated with it.
-
E.
memorialName
Indicates that a memorial is known by or designated with a particular name.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a5f3548190a6acf1dcfd64d11d |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.