Triple
T10722325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chico |
E252852
|
entity |
| Predicate | joinsGroupOf |
P23692
|
FINISHED |
| Object | hired protectors |
—
|
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: hired protectors | Statement: [Chico, joinsGroupOf, hired protectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinsGroupOf Context triple: [Chico, joinsGroupOf, hired protectors]
-
A.
memberOfGroupWith
Indicates that an entity belongs to, or is associated as a member with, a particular group or collection of entities.
-
B.
joins
chosen
Indicates that one entity becomes a member or part of another entity, typically by entering into an organization, group, or association.
-
C.
interactsWithGroup
Indicates that an entity engages in actions or exchanges with a collective group of other entities.
-
D.
formedGroup
Indicates that multiple entities have come together to create or establish a group or collective unit.
-
E.
joinedPluralityBy
Indicates that multiple entities collectively became members or participants of the same group, organization, or event through a shared act of joining.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70d44d0048190a78aae2357e864a5 |
completed | April 9, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.