Triple
T29731415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rucervus |
E752329
|
entity |
| Predicate | hasMemberWithStatus |
P153407
|
FINISHED |
| Object | rare species |
—
|
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: rare species | Statement: [Rucervus, hasMemberWithStatus, rare species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberWithStatus Context triple: [Rucervus, hasMemberWithStatus, rare species]
-
A.
hasMemberState
Indicates that an entity includes or comprises another entity as one of its constituent member states within a larger organizational or political structure.
-
B.
hasMembershipBy
Indicates that an entity holds or acquires membership in a group, organization, or program by means of a specified agent, process, or instrument.
-
C.
hasMembersWith
chosen
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
-
D.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
E.
hasGroupMember
Indicates that a group or collection includes a specific entity as one of its members.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 28, 2026, 7:42 p.m.