Triple
T12199114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angus Young |
E290665
|
entity |
| Predicate | stageAppearance |
P55800
|
FINISHED |
| Object | schoolboy uniform |
—
|
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: schoolboy uniform | Statement: [Angus Young, stageAppearance, schoolboy uniform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageAppearance Context triple: [Angus Young, stageAppearance, schoolboy uniform]
-
A.
hasStageAppearance
chosen
Indicates that an entity makes or has made a performance or appearance on a stage, typically before an audience.
-
B.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
-
C.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
D.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
-
E.
stagePortrayalIncludes
Indicates that a stage portrayal incorporates or features a particular element, character, action, or aspect within the performance.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.