Triple
T1262282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Minute Man |
E12526
|
entity |
| Predicate | inscriptionIncludesLine |
P26405
|
FINISHED |
| Object | “By the rude bridge that arched the flood” |
—
|
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: “By the rude bridge that arched the flood” | Statement: [The Minute Man, inscriptionIncludesLine, “By the rude bridge that arched the flood”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionIncludesLine Context triple: [The Minute Man, inscriptionIncludesLine, “By the rude bridge that arched the flood”]
-
A.
signatureLine
Indicates that an entity serves as a designated place or line where a signature is written or recorded.
-
B.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
C.
inscriptionType
Indicates the specific kind or category of inscription associated with an entity (e.g., dedicatory, funerary, commemorative).
-
D.
inscriptionSource
Indicates the origin or source from which an inscription was derived, created, or obtained.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- F. None of above. chosen
Provenance (4 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc77f4c8190b97a0ceaa31cfd49 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd98b62c8190a5f6710345c0537d |
completed | March 1, 2026, 10:28 p.m. |
Created at: March 1, 2026, 7:50 p.m.