Triple
T2629550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gcov |
E59599
|
entity |
| Predicate | granularity |
P12318
|
FINISHED |
| Object | per-source-line coverage |
—
|
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: per-source-line coverage | Statement: [gcov, granularity, per-source-line coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: granularity Context triple: [gcov, granularity, per-source-line coverage]
-
A.
grainSize
chosen
Indicates the relative coarseness or fineness of the material or particles involved in the relationship.
-
B.
grain
Indicates that one entity is composed of or contains a granular substance or small particles of another entity.
-
C.
precision
Indicates the degree to which an action, measurement, or outcome is carried out with exactness, minimal deviation, and fine-grained accuracy.
-
D.
resolution
Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
-
E.
fine
Indicates that an authority imposes a monetary penalty on an entity for violating a rule, law, or agreement.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdb0e7b888190bfa5d2e33f00ec0f |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd810d7f481908e81c305772c4c14 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.