Triple
T22674796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADAAA |
E560317
|
entity |
| Predicate | majorBodilyFunctionsExamples |
P68445
|
FINISHED |
| Object | immune system |
—
|
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: immune system | Statement: [ADAAA, majorBodilyFunctionsExamples, immune system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorBodilyFunctionsExamples Context triple: [ADAAA, majorBodilyFunctionsExamples, immune system]
-
A.
mainOrganOf
Indicates that one entity is the primary or central organ responsible for the core functions of another entity (such as an organism or system).
-
B.
describedHumanBodySystematically
Indicates that one entity has provided a systematic, organized description or account of the human body.
-
C.
bodyPartsGiveRiseTo
Indicates that certain body parts develop into, generate, or are the source of other anatomical structures or tissues.
-
D.
digestiveSystem
Indicates the relationship in which an entity possesses or is associated with a system responsible for breaking down food and absorbing nutrients.
-
E.
biologicalRole
chosen
Indicates the functional role or purpose that one biological entity has in relation to another or within a biological process.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178229e908190b696d14a93c11344 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:10 p.m.