Triple
T3821194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solenopsis invicta |
E84375
|
entity |
| Predicate | introducedVia |
P52482
|
FINISHED |
| Object | ballast soil |
—
|
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: ballast soil | Statement: [Solenopsis invicta, introducedVia, ballast soil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedVia Context triple: [Solenopsis invicta, introducedVia, ballast soil]
-
A.
oftenIntroducedBy
Indicates that one entity is frequently presented, mentioned, or brought into context by another entity.
-
B.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
introducedAlongWith
Indicates that one entity was introduced or presented at the same time as another entity, as part of a joint or concurrent introduction.
-
D.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
E.
introducedDuring
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef18748648190b85e62f7796ff4b4 |
completed | March 9, 2026, 4:12 p.m. |
Created at: March 9, 2026, 3:17 p.m.