Triple
T27810576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phineas |
E702507
|
entity |
| Predicate | collectiveNameWithCompanions |
P116479
|
FINISHED |
| Object | Hitchhiking Ghosts |
—
|
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: Hitchhiking Ghosts | Statement: [Phineas, collectiveNameWithCompanions, Hitchhiking Ghosts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveNameWithCompanions Context triple: [Phineas, collectiveNameWithCompanions, Hitchhiking Ghosts]
-
A.
collectiveNameForm
Indicates that one entity serves as the collective or group name form used to refer to multiple members of another entity or class.
-
B.
collectivelyKnownAs
Indicates that multiple entities are referred to together under a single shared name or designation.
-
C.
hasCompanionTeamName
chosen
Indicates that an entity is associated with a companion team identified by the given team name.
-
D.
collectiveNameInUrdu
Indicates that the given term is the collective (group) name for something when expressed in Urdu.
-
E.
hasNumberOfCompanions
Indicates the quantity of companions or associates that an entity has.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 5:42 p.m.