Triple
T3158495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Make 'Em Laugh" musical number |
E66046
|
entity |
| Predicate | usesProp |
P46693
|
FINISHED |
| Object | dummy |
—
|
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: dummy | Statement: ["Make 'Em Laugh" musical number, usesProp, dummy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProp Context triple: ["Make 'Em Laugh" musical number, usesProp, dummy]
-
A.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
B.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
-
C.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
D.
requiresProperty
Indicates that one entity depends on another entity possessing a specific property or attribute in order for a condition, action, or relationship to hold.
-
E.
usesElement
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5ed82a08190a1bdcf18ee593c79 |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada1e4f7288190a80a1672e458132d |
completed | March 8, 2026, 4:20 p.m. |
Created at: March 8, 2026, 3:05 p.m.