Triple
T24304180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sitophilus zeamais |
E612487
|
entity |
| Predicate | hasRostrum |
P155484
|
FINISHED |
| Object | elongated snout |
—
|
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: elongated snout | Statement: [Sitophilus zeamais, hasRostrum, elongated snout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRostrum Context triple: [Sitophilus zeamais, hasRostrum, elongated snout]
-
A.
hasHeadOf
Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
-
B.
hasRohe
Indicates a relationship where something is associated with, belongs to, or is located within a specific region or area (rohe).
-
C.
hasColossiOf
Indicates that one entity possesses, contains, or is characterized by monumental statues or colossal figures associated with another entity.
-
D.
hasRIO
Indicates that an entity is associated with, or possesses, a specific Region of Interest (RIO) in a given context.
-
E.
hasChambersFor
Indicates that one entity contains or provides designated chambers or compartments intended for use by another entity.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29224c7cc8190bd1a32318198326c |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:29 a.m.