Triple
T5883089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juicy Fruit |
E130795
|
entity |
| Predicate | hasTargetConsumer |
P14889
|
FINISHED |
| Object | general consumers |
—
|
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: general consumers | Statement: [Juicy Fruit, hasTargetConsumer, general consumers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetConsumer Context triple: [Juicy Fruit, hasTargetConsumer, general consumers]
-
A.
hasTarget
chosen
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
B.
hasProducer
Indicates that one entity serves as the producer or creator responsible for making or manufacturing another entity.
-
C.
isConsumedIn
Indicates that one entity is used up, ingested, or otherwise expended as part of a process, event, or action involving another entity.
-
D.
hasTargetPlatform
Indicates that something is intended to run on, be compatible with, or be deployed to a specified platform.
-
E.
hasObserver
Indicates that an entity is being watched, monitored, or examined by another entity acting as an observer.
- 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_69c0085628dc8190b334c1b44c067efc |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.