Triple
T5110220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Angels |
E115195
|
entity |
| Predicate | hasMemberClass |
P121
|
FINISHED |
| Object | angels |
—
|
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: angels | Statement: [All Angels, hasMemberClass, angels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberClass Context triple: [All Angels, hasMemberClass, angels]
-
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.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
-
D.
hasMembershipBy
Indicates that an entity holds or acquires membership in a group, organization, or program by means of a specified agent, process, or instrument.
-
E.
hasMembershipBase
Indicates that an entity possesses or is associated with a foundational group or set of members that form its membership base.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ac19e88190aa8cc8b930a58d2d |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.