Triple
T9429170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altamont Free Concert |
E227328
|
entity |
| Predicate | organizationQuality |
P88844
|
FINISHED |
| Object | poorly organized |
—
|
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: poorly organized | Statement: [Altamont Free Concert, organizationQuality, poorly organized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationQuality Context triple: [Altamont Free Concert, organizationQuality, poorly organized]
-
A.
organizationType
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
-
B.
organizationFocus
Indicates the primary area of activity, mission, or specialization that an organization is oriented toward or concentrated on.
-
C.
organizationName
Indicates that an entity has a specific official name as an organization.
-
D.
subjectOrganization
Indicates that one entity serves as the organization to which another entity (such as a person, work, or activity) is affiliated or belongs.
-
E.
organizationDescribedBy
Indicates that an organization is characterized, detailed, or explained by a particular description or document.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7c94719c81909d7743a57c45e07f |
completed | April 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:49 p.m.