Triple
T8519717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norway rat |
E201664
|
entity |
| Predicate | relevanceToHumans |
P8492
|
FINISHED |
| Object | major laboratory animal |
—
|
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: major laboratory animal | Statement: [Norway rat, relevanceToHumans, major laboratory animal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relevanceToHumans Context triple: [Norway rat, relevanceToHumans, major laboratory animal]
-
A.
relationshipToHumans
chosen
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
B.
providesToHumans
Indicates that one entity supplies, furnishes, or makes something available for use or benefit by humans.
-
C.
isHumanOfInterest
Indicates that the person is considered noteworthy, relevant, or significant within a particular context or analysis.
-
D.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
E.
conservationRelevance
Indicates that something has significance or importance for conservation efforts, such as protecting species, habitats, or ecosystems.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe627de908190b463da0f26da4ffb |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.