Triple
T4021343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Scholar |
E91284
|
entity |
| Predicate | computesMetric |
P49064
|
FINISHED |
| Object | h-index |
—
|
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: h-index | Statement: [Google Scholar, computesMetric, h-index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computesMetric Context triple: [Google Scholar, computesMetric, h-index]
-
A.
metricComponent
Indicates a relationship where one element functions as a component or constituent part of a larger metric.
-
B.
metricType
Indicates the specific category or kind of measurement that a given metric represents.
-
C.
distanceMetric
Indicates a quantitative measure of how far apart two entities are within a given space or according to a specified metric.
-
D.
isUsedToCompute
chosen
Indicates that one entity serves as an input, basis, or resource for performing a calculation or deriving a result about another entity.
-
E.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefacb4c208190b8dd595a534850b2 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.