Triple
T8632165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sciurus vulgaris |
E204427
|
entity |
| Predicate | competedBy |
P1375
|
FINISHED |
| Object | Sciurus carolinensis |
—
|
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: Sciurus carolinensis | Statement: [Sciurus vulgaris, competedBy, Sciurus carolinensis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competedBy Context triple: [Sciurus vulgaris, competedBy, Sciurus carolinensis]
-
A.
competedFor
Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
-
B.
competedAs
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
C.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
D.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
E.
competesWith
chosen
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.