Triple
T1741901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moschus |
E38250
|
entity |
| Predicate | hasMuskGlandLocation |
P31788
|
FINISHED |
| Object | between navel and genitals in males |
—
|
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: between navel and genitals in males | Statement: [Moschus, hasMuskGlandLocation, between navel and genitals in males]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMuskGlandLocation Context triple: [Moschus, hasMuskGlandLocation, between navel and genitals in males]
-
A.
hasSaltGlands
Indicates that an organism possesses specialized glands used to excrete excess salt from its body.
-
B.
hasExcretorySystem
Indicates that an organism possesses a biological system responsible for eliminating metabolic waste products from its body.
-
C.
hasTissue
Indicates that one entity possesses, contains, or is associated with a specific tissue of another entity.
-
D.
hasBodyCavity
Indicates that an organism possesses an internal body cavity or space within its body structure.
-
E.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
- F. None of above. chosen
Provenance (4 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab3c2479148190badc616f8e2686d4 |
completed | March 6, 2026, 8:42 p.m. |
Created at: March 4, 2026, 7:30 p.m.