Triple
T35527710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rick Rude |
E1026714
|
entity |
| Predicate | notableEntranceFeature |
P174764
|
FINISHED |
| Object | airbrushed tights |
—
|
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: airbrushed tights | Statement: [Rick Rude, notableEntranceFeature, airbrushed tights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEntranceFeature Context triple: [Rick Rude, notableEntranceFeature, airbrushed tights]
-
A.
hasLandmarkAtEntrance
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
-
B.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
C.
entranceTrait
chosen
Indicates a characteristic or feature associated with how an entity enters or is accessed (e.g., through a particular type or style of entrance).
-
D.
doorwayFeature
Indicates that one entity is a feature, characteristic, or structural element specifically associated with a doorway of another entity.
-
E.
hasEntranceStructure
Indicates that one entity possesses or is associated with a specific physical structure that serves as its entrance.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.