Triple
T15035229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polly |
E378461
|
entity |
| Predicate | hasCompanionStatus |
P27935
|
FINISHED |
| Object | main companion |
—
|
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 companion | Statement: [Polly, hasCompanionStatus, main companion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionStatus Context triple: [Polly, hasCompanionStatus, main companion]
-
A.
companionshipStatus
chosen
Indicates the current state or condition of a relationship of companionship between two or more entities.
-
B.
hasCompanionCandidate
Indicates that an entity is associated with another entity that is being considered or proposed as a potential companion.
-
C.
hasCompanionPillar
Indicates that an entity is associated with or supported by a corresponding companion pillar.
-
D.
hasCompanionEvent
Indicates that one event is associated with another event that occurs alongside it as a related or accompanying occurrence.
-
E.
hasCompanionOrganization
Indicates that one organization is associated with another organization that accompanies, supports, or partners it in some related capacity.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82b29948190acda49cbec3f927a |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:59 a.m.