Triple
T18774148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philotes |
E459090
|
entity |
| Predicate | conceptGroup |
P60805
|
FINISHED |
| Object | personifications of social forces |
—
|
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: personifications of social forces | Statement: [Philotes, conceptGroup, personifications of social forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptGroup Context triple: [Philotes, conceptGroup, personifications of social forces]
-
A.
cultGroupOf
Indicates that one entity is a cult group to which the other entity belongs or is affiliated.
-
B.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
C.
categoryConcept
chosen
Indicates that one entity serves as a categorical type or conceptual class under which the other entity is grouped or classified.
-
D.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
E.
controlGroup
Indicates that one entity functions as the control group against which another condition, treatment, or experimental group is compared.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933888408190a21f9ac5b360d1eb |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.