Triple
T12389901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Michigan Credit Union |
E295962
|
entity |
| Predicate | memberOwned |
P104706
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lake Michigan Credit Union, memberOwned, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOwned Context triple: [Lake Michigan Credit Union, memberOwned, true]
-
A.
membershipBased
Indicates that access, participation, or inclusion in something is conditional on holding a membership or belonging to a defined group.
-
B.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
-
C.
membershipUnit
Indicates that an entity belongs to, is part of, or is counted within a particular unit, group, or organizational subdivision.
-
D.
membershipConsistsOf
Indicates that a membership is composed of, or includes, specific member entities as its constituents.
-
E.
membershipStatus
Indicates the current state or level of an entity’s participation or affiliation within a group, organization, or program.
- F. None of above. chosen
Provenance (4 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fcf6aa8819080c9a2407a72db2e |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93fa244148190a960be3ff6f1cf45 |
completed | April 10, 2026, 6:21 p.m. |
Created at: April 8, 2026, 9:54 p.m.