Triple
T23760273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nine-turn Large Intestine |
E587229
|
entity |
| Predicate | preparationComplexity |
P28756
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Nine-turn Large Intestine, preparationComplexity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparationComplexity Context triple: [Nine-turn Large Intestine, preparationComplexity, high]
-
A.
typicalComplexity
Indicates the usual or characteristic level of complexity associated with an entity, process, or situation.
-
B.
preparationInvolved
Indicates that a particular preparation, process, or setup is involved in enabling or carrying out an action, event, or relationship.
-
C.
hasComplexity
chosen
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
D.
preparationPreference
Indicates how an entity prefers something to be prepared, processed, or made ready (e.g., style, method, or conditions of preparation).
-
E.
typicalPreparation
Indicates the usual or standard way in which something is prepared or made.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb1d6348190afb3f0fbea1b9ca3 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.