Triple
T16113623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takoma Park Folk Festival |
E390942
|
entity |
| Predicate | hasFamilyOrientation |
P121525
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Takoma Park Folk Festival, hasFamilyOrientation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyOrientation Context triple: [Takoma Park Folk Festival, hasFamilyOrientation, true]
-
A.
familyPolicyOrientation
Indicates how a policy or actor is oriented toward family-related issues, such as the extent to which it supports, prioritizes, or affects families and family life.
-
B.
hasFamilySituation
Indicates the familial status or circumstances that apply to an entity, such as their family composition, responsibilities, or living situation.
-
C.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
D.
religiousOrientationOfParent
Indicates that a parent has a particular religious orientation or affiliation.
-
E.
hasFamilyFriend
Indicates that one entity has another entity as a friend who is connected through family ties or close familial relationships.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20168bf98819093c3260d4fde2b53 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.