Triple
T36350585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Slam 2009 |
E895190
|
entity |
| Predicate | alsoSecured |
P185154
|
FINISHED |
| Object | Triple Crown |
—
|
NE NERFINISHED |
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: Triple Crown | Statement: [Grand Slam 2009, alsoSecured, Triple Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoSecured Context triple: [Grand Slam 2009, alsoSecured, Triple Crown]
-
A.
securedAgainst
Indicates that one entity is protected or safeguarded against threats, risks, or harmful actions originating from another entity or source.
-
B.
securedVia
Indicates that something is protected, authenticated, or made safe through a specified method, mechanism, or channel.
-
C.
securedVariant
Indicates that one entity is a security-enhanced or more protected version of another entity.
-
D.
isSecureFor
Indicates that one entity provides a level of protection or safety that makes it appropriate or safe for use, access, or interaction by another entity.
-
E.
securedStatus
Indicates that an entity’s state, access, or data has been protected or locked down to prevent unauthorized use or modification.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bb3f23f48190b0b9c2d667e09b52 |
completed | May 3, 2026, 9:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.