Triple
T24902928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITF Pace Category 3 (medium) |
E623627
|
entity |
| Predicate | inSchemeWith |
P157862
|
FINISHED |
| Object | ITF Pace Category 5 (fast) |
—
|
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: ITF Pace Category 5 (fast) | Statement: [ITF Pace Category 3 (medium), inSchemeWith, ITF Pace Category 5 (fast)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inSchemeWith Context triple: [ITF Pace Category 3 (medium), inSchemeWith, ITF Pace Category 5 (fast)]
-
A.
inSchemeWith
chosen
Indicates that two entities are associated with, or categorized under, the same conceptual scheme or classification system.
-
B.
usesScheme
Indicates that one entity employs, follows, or is based on a particular scheme, method, or structured plan associated with another entity.
-
C.
notableScheme
Indicates that an entity is particularly recognized or prominent within a specific scheme, system, or organizational framework.
-
D.
similarSchemeIn
Indicates that one entity uses a scheme or structural pattern that is similar to that used in another entity.
-
E.
statutoryScheme
Indicates that one entity is part of, governed by, or defined within a particular statutory or legislative framework.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:27 a.m.