Triple
T37256201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Cogswell |
E924133
|
entity |
| Predicate | competesWithCompany |
P1375
|
FINISHED |
| Object | Spacely Space Sprockets |
—
|
NE NERFINISHED |
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: Spacely Space Sprockets | Statement: [Mr. Cogswell, competesWithCompany, Spacely Space Sprockets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competesWithCompany Context triple: [Mr. Cogswell, competesWithCompany, Spacely Space Sprockets]
-
A.
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.
-
B.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
C.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
D.
tieneCompetencia
Indicates that one entity has or faces competition from another entity.
-
E.
underlyingCompanyMajorCompetitor
Indicates that one company serves as a primary or significant competitor to another company.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 3, 2026, 4:15 p.m.