Triple
T36520790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LWV |
E900174
|
entity |
| Predicate | relatedEntityType |
—
|
GENERATED |
| Object | 501(c)(3) organization |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEntityType Context triple: [LWV, relatedEntityType, 501(c)(3) organization]
-
A.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
B.
includedEntityType
Indicates that one entity type is contained within, or forms a component part of, another entity type.
-
C.
relatedNamedEntity
Indicates that two entities are connected through a shared or associated proper name (e.g., person, organization, location, or other named entity).
-
D.
successorOrRelatedEntity
Indicates that one entity is a successor to, or otherwise closely related in lineage or function to, another entity.
-
E.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
- F. None of above.
Provenance (1 batch)
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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.