Triple
T15753721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaps and Verges |
E381911
|
entity |
| Predicate | fieldInfluencingWork |
P72626
|
FINISHED |
| Object | chemistry |
—
|
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: chemistry | Statement: [Gaps and Verges, fieldInfluencingWork, chemistry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldInfluencingWork Context triple: [Gaps and Verges, fieldInfluencingWork, chemistry]
-
A.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
B.
relatedWorkField
Indicates that one work is associated with or pertains to the same or a relevant field, discipline, or area of activity as another work.
-
C.
influencedWork
Indicates that one work has had a significant impact on the creation, style, content, or development of another work.
-
D.
workImpact
chosen
Indicates that one entity’s work has an effect or influence on another entity, situation, or outcome.
-
E.
fieldOfSignificance
Indicates that something holds particular importance, relevance, or impact within a specified domain, context, or area of interest.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.