Triple
T32189681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annabeth Nass |
E822202
|
entity |
| Predicate | relationshipTypeInSeries |
P10690
|
FINISHED |
| Object | friendship with Zoe Hart |
—
|
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: friendship with Zoe Hart | Statement: [Annabeth Nass, relationshipTypeInSeries, friendship with Zoe Hart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeInSeries Context triple: [Annabeth Nass, relationshipTypeInSeries, friendship with Zoe Hart]
-
A.
seriesRelation
Indicates a relationship where one entity is part of, follows from, or is otherwise connected to another within an ordered series or sequence.
-
B.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
C.
showsRelationshipWith
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with another entity.
-
D.
relationshipTypeStart
Indicates the type or category of relationship that begins or is initiated at a specific point or event.
-
E.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:35 a.m.