Triple
T10990725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GREVIO |
E259746
|
entity |
| Predicate | memberCriteria |
P45671
|
FINISHED |
| Object | high moral character |
—
|
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: high moral character | Statement: [GREVIO, memberCriteria, high moral character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberCriteria Context triple: [GREVIO, memberCriteria, high moral character]
-
A.
membershipCondition
chosen
Indicates the rule, requirement, or criterion that determines whether an entity qualifies for membership in a given group or set.
-
B.
hasMemberCriteria
Indicates that a group, collection, or set is defined or constrained by specific criteria that its members must satisfy.
-
C.
membershipField
Indicates that one entity serves as a field or attribute capturing the membership status or association of another entity within a group, organization, or collection.
-
D.
membersTermIs
Indicates that a member or group of members is associated with, or serves for, a specific term or period of office.
-
E.
memberCategory
Indicates that an entity belongs to or is classified under a specific category or 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d787b8d7088190b7d6b63c3bac4ad1 |
completed | April 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.