Triple
T25160973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PKI |
E626436
|
entity |
| Predicate | claimedMembers |
P158192
|
FINISHED |
| Object | around 3 million |
—
|
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: around 3 million | Statement: [PKI, claimedMembers, around 3 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedMembers Context triple: [PKI, claimedMembers, around 3 million]
-
A.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
B.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
-
C.
claimedIn
Indicates that a statement, fact, or assertion is reported or documented within a particular source, document, or claim.
-
D.
creditedMember
Indicates that a particular member is formally acknowledged or recognized as having contributed to or been responsible for something.
-
E.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f46b8d45548190a5bdb4fba1d3ba4e |
completed | May 1, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 6:31 a.m.