Triple
T6717983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blandings Castle |
E153319
|
entity |
| Predicate | hasServantInFiction |
P61558
|
FINISHED |
| Object | Beach |
—
|
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: Beach | Statement: [Blandings Castle, hasServantInFiction, Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServantInFiction Context triple: [Blandings Castle, hasServantInFiction, Beach]
-
A.
hasServant
Indicates that one entity has another entity serving it in a subordinate or attendant role.
-
B.
hasNotableFictionalBearer
Indicates that an entity is associated with at least one well-known fictional character that bears its name or designation.
-
C.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
D.
hasFictionalStaffMember
chosen
Indicates that an entity includes or employs a staff member who is a fictional character.
-
E.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d12765a48190b485176dc2ffa0fa |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.