Triple
T35265966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Care Package |
E1018513
|
entity |
| Predicate | isCompanionWorkTo |
P147590
|
FINISHED |
| Object | main project by Scorpion |
—
|
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: main project by Scorpion | Statement: [Care Package, isCompanionWorkTo, main project by Scorpion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCompanionWorkTo Context triple: [Care Package, isCompanionWorkTo, main project by Scorpion]
-
A.
includesCompanion
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
B.
associatedWithWorkOf
Indicates that one entity has a connection or involvement with the work, creation, or output produced by another entity.
-
C.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
-
D.
hasTwinWork
chosen
Indicates that one work has a corresponding counterpart considered its twin, typically due to strong similarity, parallel creation, or intentional pairing.
-
E.
hasCompanionColleague
Indicates that one entity has another entity as a colleague who also serves as a companion or close associate.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f9a095881908d7d5d1914afae77 |
completed | May 3, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.