Triple
T33233348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budgie the Little Helicopter |
E850758
|
entity |
| Predicate | hasAnthropomorphicCharacter |
P26660
|
FINISHED |
| Object | helicopter |
—
|
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: helicopter | Statement: [Budgie the Little Helicopter, hasAnthropomorphicCharacter, helicopter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnthropomorphicCharacter Context triple: [Budgie the Little Helicopter, hasAnthropomorphicCharacter, helicopter]
-
A.
isAnthropomorphic
chosen
Indicates that something non-human is given human-like characteristics, form, or behavior.
-
B.
hasAnthropomorphicAnimals
Indicates that something features animals with human-like characteristics, behaviors, or roles.
-
C.
hasAnimatronicCharacter
Indicates that an entity features, includes, or is associated with an animatronic character.
-
D.
hasFictionalAgriculturalCharacter
Indicates that an entity features or includes a character associated with agriculture within a fictional context.
-
E.
nonHumanCharacter
Indicates that the character involved in the relation is not a human being (e.g., an animal, creature, AI, or other non-human 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 1, 2026, 1:31 a.m.