Triple
T7227821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .IXIC |
E154825
|
entity |
| Predicate | isUsedAsBenchmark |
P23745
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [.IXIC, isUsedAsBenchmark, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedAsBenchmark Context triple: [.IXIC, isUsedAsBenchmark, true]
-
A.
benchmarkFor
chosen
Indicates that one entity serves as a standard or reference point against which the performance, quality, or characteristics of another entity are measured or evaluated.
-
B.
isUsedToTest
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
-
C.
primaryBenchmarkProvider
Indicates that one entity serves as the main or default source of benchmark data or performance standards for another entity.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
isUsedToCompute
Indicates that one entity serves as an input, basis, or resource for performing a calculation or deriving a result about another entity.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9df72cc81908d1c04e6e310fbb4 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.