Triple
T33637421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Orioles Hall of Fame |
E861733
|
entity |
| Predicate | hasPhysicalDisplay |
P127197
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Baltimore Orioles Hall of Fame, hasPhysicalDisplay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalDisplay Context triple: [Baltimore Orioles Hall of Fame, hasPhysicalDisplay, yes]
-
A.
hasPhysicalDisplays
chosen
Indicates that an entity possesses one or more tangible, visible display units or interfaces.
-
B.
hasPhysicalKeypad
Indicates that an entity is equipped with a tangible, button-based keypad for input or control.
-
C.
canBeDisplayedOn
Indicates that something is capable of being shown or rendered on a particular medium, device, or interface.
-
D.
hasFormFactor
Indicates that one entity possesses or is characterized by a particular physical or structural form factor defined by another entity.
-
E.
supportsDisplayTechnology
Indicates that one entity is compatible with, or capable of operating using, a specified display technology.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:42 a.m.