Triple
T22128405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Like a Surgeon |
E546847
|
entity |
| Predicate | typicalConcertProps |
P147100
|
FINISHED |
| Object | surgical scrubs |
—
|
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: surgical scrubs | Statement: [Like a Surgeon, typicalConcertProps, surgical scrubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalConcertProps Context triple: [Like a Surgeon, typicalConcertProps, surgical scrubs]
-
A.
typicalBilletsInclude
Indicates that certain items or roles are commonly or normally included within a given set of billets.
-
B.
typicalPerformerCount
Indicates the usual or standard number of performers involved in carrying out the associated activity or event.
-
C.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
D.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
E.
notableConcert
Indicates that a concert event is recognized as particularly significant, memorable, or influential in some notable way.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12983acfc81908013f66acb31f198 |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:32 p.m.