Triple
T17199645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susan Foreman |
E417442
|
entity |
| Predicate | companionGroup |
P115046
|
FINISHED |
| Object | First Doctor original TARDIS team |
—
|
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: First Doctor original TARDIS team | Statement: [Susan Foreman, companionGroup, First Doctor original TARDIS team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionGroup Context triple: [Susan Foreman, companionGroup, First Doctor original TARDIS team]
-
A.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
B.
groupTogether
chosen
Indicates that multiple entities are treated or arranged as a single collective unit or set.
-
C.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
D.
companionsCategory
Indicates that one entity is classified under a specific category related to companions or companionship.
-
E.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42daddcd08190a82f36c940bf3f7b |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.