Triple
T15888320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trentham Monkey Forest |
E385246
|
entity |
| Predicate | hasMonkeyGroups |
P68099
|
FINISHED |
| Object | multiple social groups |
—
|
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: multiple social groups | Statement: [Trentham Monkey Forest, hasMonkeyGroups, multiple social groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonkeyGroups Context triple: [Trentham Monkey Forest, hasMonkeyGroups, multiple social groups]
-
A.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
B.
hasObjectGroup
Indicates that an entity is associated with a specific group or collection of objects treated as a single unit.
-
C.
hasGroupStructure
Indicates that the related entities together form an algebraic group under a specified operation, satisfying closure, associativity, identity, and invertibility.
-
D.
hasFaunaGroup
chosen
Indicates that an entity possesses, contains, or is associated with a particular group or assemblage of animal life.
-
E.
hasSecondaryUserGroup
Indicates that an entity is associated with an additional, non-primary user group beyond its main group.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.