Triple
T3728939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEA |
E79014
|
entity |
| Predicate | hasMembersType |
P121
|
FINISHED |
| Object | individual members |
—
|
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: individual members | Statement: [UEA, hasMembersType, individual members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMembersType Context triple: [UEA, hasMembersType, individual members]
-
A.
hasMemberType
chosen
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
B.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
C.
hasMemberCountType
Indicates the type or classification used to describe how the number of members in a group or collection is represented.
-
D.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
-
E.
hasMemberFromEach
Indicates that a group or collection includes at least one member originating from each specified category, set, or subgroup.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb17432881909390284b935ed3fd |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.