Triple
T20511086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavendish bananas |
E503561
|
entity |
| Predicate | typicalUseStage |
P106948
|
FINISHED |
| Object | fully yellow with few brown spots |
—
|
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: fully yellow with few brown spots | Statement: [Cavendish bananas, typicalUseStage, fully yellow with few brown spots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseStage Context triple: [Cavendish bananas, typicalUseStage, fully yellow with few brown spots]
-
A.
typicalUsagePhase
chosen
Indicates the phase or stage in which something is most commonly or characteristically used.
-
B.
usedInStage
Indicates that something is utilized or applied during a particular stage or phase of a process or workflow.
-
C.
usedStage
Indicates that an entity made use of a particular stage or phase within a process, workflow, or lifecycle.
-
D.
usesStageType
Indicates that one entity employs or operates with a particular type or category of stage.
-
E.
usesStage
Indicates that one entity employs or operates on another entity at a particular phase or stage within a process or workflow.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dcb8f5c8190b0d4c09f3669a8ec |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.