Triple
T6925592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clear Lake AVA |
E160298
|
entity |
| Predicate | moderatingInfluence |
P34126
|
FINISHED |
| Object | large inland lake |
—
|
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: large inland lake | Statement: [Clear Lake AVA, moderatingInfluence, large inland lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moderatingInfluence Context triple: [Clear Lake AVA, moderatingInfluence, large inland lake]
-
A.
moderation
Indicates that an entity exercises restraint, balance, or avoidance of extremes in its actions, behavior, or use of resources.
-
B.
moderator
Indicates that one entity serves as a moderator for another entity, overseeing, managing, or facilitating its activities, interactions, or content.
-
C.
modulates
chosen
Indicates that one entity adjusts, regulates, or alters the intensity, frequency, or effect of another entity or process.
-
D.
usesModerator
Indicates that an entity employs or relies on a moderator to oversee, regulate, or manage its interactions or processes.
-
E.
influencedDiscussionOf
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
- 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da18b6388190947dfc1eb9e5d382 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.