Triple
T11472605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little People, Big World |
E271944
|
entity |
| Predicate | hasCastMemberWithCondition |
P99470
|
FINISHED |
| Object | achondroplasia |
—
|
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: achondroplasia | Statement: [Little People, Big World, hasCastMemberWithCondition, achondroplasia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCastMemberWithCondition Context triple: [Little People, Big World, hasCastMemberWithCondition, achondroplasia]
-
A.
hasCast
Indicates that a creative work features a particular group of performers or actors.
-
B.
includesCastMembersFrom
Indicates that one entity’s cast list contains one or more cast members who also appear in the cast list of another entity.
-
C.
hasCrewMember
Indicates that an entity includes or employs another entity as a member of its crew.
-
D.
castMemberWith
Indicates that one entity is a cast member appearing together with another specified entity in the same production or work.
-
E.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
- F. None of above. chosen
Provenance (4 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294b3f388190a587c358313f7260 |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:35 p.m.