Triple
T35302650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ayam rica-rica |
E1019543
|
entity |
| Predicate | canUseProtein |
P9928
|
FINISHED |
| Object | free-range chicken |
—
|
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: free-range chicken | Statement: [ayam rica-rica, canUseProtein, free-range chicken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseProtein Context triple: [ayam rica-rica, canUseProtein, free-range chicken]
-
A.
hasProtein
Indicates that one entity contains, includes, or is associated with a specific protein.
-
B.
isProtein
Indicates that the subject entity is classified as a protein.
-
C.
canUse
chosen
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
D.
mainProtein
Indicates that one protein is the primary or central protein in relation to another entity, such as a complex, pathway, or interaction context.
-
E.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904becb8819099bfe08009854ba5 |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.