Triple
T35843481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kryptonian guild system |
E1036148
|
entity |
| Predicate | membershipChange |
P143566
|
FINISHED |
| Object | rare |
—
|
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: rare | Statement: [Kryptonian guild system, membershipChange, rare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipChange Context triple: [Kryptonian guild system, membershipChange, rare]
-
A.
memberBecame
Indicates that an entity transitioned into becoming a member of a group, organization, or collection at a specific point in time.
-
B.
leagueMembershipChange
Indicates a change in an entity’s affiliation with a league, such as joining, leaving, or switching leagues.
-
C.
relationshipChange
chosen
Indicates a change in the type, status, or nature of a relationship between entities over time.
-
D.
memberOf
Indicates that an entity belongs to, is part of, or is a constituent of a larger group, organization, or collection.
-
E.
membershipTransfer
Indicates the transfer of membership status, rights, or affiliation from one entity to another.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:06 p.m.