Triple
T36508762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRB World Rankings |
E899840
|
entity |
| Predicate | excludesMatchType |
P3119
|
FINISHED |
| Object | non-capped matches |
—
|
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: non-capped matches | Statement: [IRB World Rankings, excludesMatchType, non-capped matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludesMatchType Context triple: [IRB World Rankings, excludesMatchType, non-capped matches]
-
A.
excludesMode
Indicates that one mode, option, or operational state is defined as incompatible with and therefore prevents the use of another mode.
-
B.
includesMatchType
Indicates that one entity’s set or collection contains an element with a specified type of match (e.g., exact, partial, or pattern-based) to another entity.
-
C.
excludes
chosen
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
D.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
E.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.