Triple
T26205067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | norepinephrine |
E655337
|
entity |
| Predicate | isEndogenousTo |
P160042
|
FINISHED |
| Object | mammals |
—
|
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: mammals | Statement: [norepinephrine, isEndogenousTo, mammals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndogenousTo Context triple: [norepinephrine, isEndogenousTo, mammals]
-
A.
isEndogenousTo
chosen
Indicates that something originates from, is produced within, or is internally determined by the system, organism, or context it is associated with.
-
B.
isItsOwn
Indicates that an entity stands in the specified relation to itself, i.e., it is related to itself as its own counterpart or owner.
-
C.
isExternalTo
Indicates that one entity exists or operates outside the boundaries, scope, or domain of another entity.
-
D.
isEndonym
Indicates that a name is used by a group to refer to themselves or their own place/language, rather than being an external or foreign designation.
-
E.
isNonEndonymFor
Indicates that a given name for a place, people, or language is used by outsiders and is not the name used by the group or locale itself.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cde512c819094036b09613ff330 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:50 p.m.