Triple
T9601712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | softball |
E231864
|
entity |
| Predicate | allowsSubstitutions |
P51430
|
FINISHED |
| Object | re-entry rules vary by code |
—
|
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: re-entry rules vary by code | Statement: [softball, allowsSubstitutions, re-entry rules vary by code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsSubstitutions Context triple: [softball, allowsSubstitutions, re-entry rules vary by code]
-
A.
involvesSubstitute
chosen
Indicates that one entity participates in a situation, event, or role as a replacement or stand-in for another entity.
-
B.
numberOfSubstitutes
Indicates the quantity of substitute entities associated with or allowed for a given entity or situation.
-
C.
allowsSublicensing
Indicates that one party grants another the right to further license the same rights to additional third parties.
-
D.
permitsExpansionOf
Indicates that one entity authorizes or enables the enlargement, extension, or increase in scope of another entity.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a3a49608190ad1f65195e4d5cda |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.