Triple
T17359829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston Astros Hall of Fame |
E422036
|
entity |
| Predicate | hasPhysicalDisplays |
P127197
|
FINISHED |
| Object | plaques of inductees |
—
|
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: plaques of inductees | Statement: [Houston Astros Hall of Fame, hasPhysicalDisplays, plaques of inductees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalDisplays Context triple: [Houston Astros Hall of Fame, hasPhysicalDisplays, plaques of inductees]
-
A.
hasNumberOfScreens
Indicates the quantity of screens associated with or contained in a given entity.
-
B.
hasPhysicalKeypad
Indicates that an entity is equipped with a tangible, button-based keypad for input or control.
-
C.
supportsDisplayTechnology
Indicates that one entity is compatible with, or capable of operating using, a specified display technology.
-
D.
hasFormFactor
Indicates that one entity possesses or is characterized by a particular physical or structural form factor defined by another entity.
-
E.
supportsExternalDisplay
Indicates that an entity is capable of connecting to and functioning with an external display device.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4be7448190988593ee342348c1 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.