Triple
T7981389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio of the South |
E185577
|
entity |
| Predicate | intendedMembers |
P2776
|
FINISHED |
| Object | like-minded painters |
—
|
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: like-minded painters | Statement: [Studio of the South, intendedMembers, like-minded painters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedMembers Context triple: [Studio of the South, intendedMembers, like-minded painters]
-
A.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
B.
primaryMembers
Indicates that the related entities are the main or most important members within a larger group or organization.
-
C.
typicalMembers
chosen
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
D.
additionalMembersMethod
Indicates the method or process by which additional members are added or included in a group, system, or structure.
-
E.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c28cb108190bca697600bbbf53b |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.