Triple
T8519679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norway rat |
E201664
|
entity |
| Predicate | associationWithHumans |
P83090
|
FINISHED |
| Object | commensal |
—
|
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: commensal | Statement: [Norway rat, associationWithHumans, commensal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associationWithHumans Context triple: [Norway rat, associationWithHumans, commensal]
-
A.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
associatedWithAnimal
Indicates a relationship where an entity has a connection, link, or relevance to an animal.
-
C.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
-
D.
associatedBeings
Indicates that two or more beings are linked or connected to each other in some relevant way.
-
E.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
- 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_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. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:16 p.m.