Triple
T25206358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Clinging Vine |
E631261
|
entity |
| Predicate | hasStarBilling |
P167251
|
FINISHED |
| Object | Leatrice Joy |
—
|
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: Leatrice Joy | Statement: [The Clinging Vine, hasStarBilling, Leatrice Joy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStarBilling Context triple: [The Clinging Vine, hasStarBilling, Leatrice Joy]
-
A.
usesBillingModel
Indicates that one entity applies or operates under a particular billing model for charging or pricing purposes.
-
B.
hasStarOn
Indicates that one entity bears or displays a star symbol positioned on another entity.
-
C.
hasStars
Indicates that an entity possesses or is associated with one or more stars.
-
D.
usesBillFor
Indicates that one entity employs, relies on, or makes use of a particular bill (such as a legislative proposal, invoice, or statement) for a specific purpose or action.
-
E.
hasStripe
Indicates that one entity possesses or exhibits a stripe or stripes as a characteristic or feature.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 21, 2026, 12:52 p.m.