Triple
T35452127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A.C.T. |
E1024663
|
entity |
| Predicate | hasArtisticMission |
P130880
|
FINISHED |
| Object | producing high-quality theater |
—
|
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: producing high-quality theater | Statement: [A.C.T., hasArtisticMission, producing high-quality theater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisticMission Context triple: [A.C.T., hasArtisticMission, producing high-quality theater]
-
A.
hasArtisticFocus
Indicates that an entity’s primary artistic attention, theme, or specialization is directed toward a particular subject, style, or medium.
-
B.
hasArtisticStrategy
Indicates that an entity employs or is associated with a particular artistic approach, method, or plan in creating or presenting art.
-
C.
hasCreativeMission
chosen
Indicates that an entity is engaged in or guided by a specific creative purpose, goal, or overarching artistic objective.
-
D.
hasArtisticActivity
Indicates that an entity engages in, participates in, or is associated with an artistic activity or creative practice.
-
E.
artisticAmbition
Indicates a desire or drive to create, achieve, or excel in artistic or creative pursuits.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:04 p.m.