Triple
T36520790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LWV |
E900174
|
entity |
| Predicate | relatedEntityType |
P37
|
FINISHED |
| Object | 501(c)(3) organization |
—
|
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: 501(c)(3) organization | Statement: [LWV, relatedEntityType, 501(c)(3) organization]
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 (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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.