Triple
T25020668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giambi ed epodi |
E626560
|
entity |
| Predicate | metricalExperimentation |
P157547
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Giambi ed epodi, metricalExperimentation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricalExperimentation Context triple: [Giambi ed epodi, metricalExperimentation, yes]
-
A.
parallelExperiment
Indicates that one experiment is conducted alongside another under comparable conditions, typically for simultaneous testing or comparison.
-
B.
majorExperiment
Indicates that an entity conducts or is involved in a primary, large-scale, or most significant experiment in a given context.
-
C.
experimentedOn
Indicates that one entity conducted experiments or tests on another entity as the subject of investigation.
-
D.
experiment
Indicates that an entity conducts, participates in, or is the subject of a controlled test or trial to observe outcomes or validate hypotheses.
-
E.
includesExperiment
Indicates that one entity contains or encompasses a specific experiment as part of its scope, composition, or content.
- F. None of above. chosen
Provenance (4 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44ba9d564819087d3b9041bb0205b |
completed | May 1, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:06 a.m.