Triple
T29372210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YM-2151 |
E744882
|
entity |
| Predicate | hasFeedbackFunction |
P175350
|
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: [YM-2151, hasFeedbackFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeedbackFunction Context triple: [YM-2151, hasFeedbackFunction, yes]
-
A.
hasFeedbackType
Indicates that an entity is associated with a specific category or type of feedback it provides or receives.
-
B.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
C.
hasJudgingFunction
Indicates that an entity holds a role or capacity to evaluate, assess, or make judgments about another entity or situation.
-
D.
hasDamFunction
Indicates that something serves the role or performs the function of a dam, such as impounding or regulating the flow of water.
-
E.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 28, 2026, 2:28 p.m.