Triple
T35784845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlisle swap meets |
E1034536
|
entity |
| Predicate | typicalAttendeesFrom |
P206047
|
FINISHED |
| Object | across the United States |
—
|
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: across the United States | Statement: [Carlisle swap meets, typicalAttendeesFrom, across the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAttendeesFrom Context triple: [Carlisle swap meets, typicalAttendeesFrom, across the United States]
-
A.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
B.
customaryAttendee
Indicates that an entity habitually or traditionally attends a particular event, gathering, or type of occasion.
-
C.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
D.
traditionalParticipantsType
Indicates the type or category of participants involved in a traditional or customary context or activity.
-
E.
typicalGuests
Indicates the usual or most common guests associated with a particular host, place, or event.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.