Triple
T35596111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harriet Tubman Square |
E1028634
|
entity |
| Predicate | isNamedForRoleOf |
P24365
|
FINISHED |
| Object | Underground Railroad conductor |
—
|
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: Underground Railroad conductor | Statement: [Harriet Tubman Square, isNamedForRoleOf, Underground Railroad conductor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedForRoleOf Context triple: [Harriet Tubman Square, isNamedForRoleOf, Underground Railroad conductor]
-
A.
isNamedForEponymRole
Indicates that one entity bears a name derived from another entity that serves as its eponym or namesake.
-
B.
hasNamedForRole
Indicates that an entity has been given a specific name or label that corresponds to a particular role it plays.
-
C.
isNamedFor
chosen
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
D.
hasNamesakeRoleFor
Indicates that one entity holds a role or position that is named after, or serves as a namesake for, another entity.
-
E.
isNamedForPersonFrom
Indicates that an entity is named after a person who originates from a specified place or region.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.