Triple
T13035267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riprap |
E326544
|
entity |
| Predicate | authorInfluenceOn |
P38337
|
FINISHED |
| Object | contemporary environmental poetry |
—
|
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: contemporary environmental poetry | Statement: [Riprap, authorInfluenceOn, contemporary environmental poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorInfluenceOn Context triple: [Riprap, authorInfluenceOn, contemporary environmental poetry]
-
A.
influencedScholar
Indicates that one scholar has had a significant intellectual or academic impact on another scholar’s work, ideas, or development.
-
B.
impactOnAuthor
Indicates that one entity has an effect, influence, or consequence on the author.
-
C.
authorMentionedBy
Indicates that a given author is referenced or cited by another entity (such as a document, work, or person).
-
D.
wereInfluencedBy
Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
-
E.
influencedPerson
chosen
Indicates that one entity has affected, shaped, or guided the thoughts, behavior, or development of another person.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97effca908190ab89fdb034e02680 |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:55 p.m.