Triple
T18641118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Elmo |
E455686
|
entity |
| Predicate | memberSelectionProcess |
P126
|
FINISHED |
| Object | selective tap process |
—
|
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: selective tap process | Statement: [St. Elmo, memberSelectionProcess, selective tap process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberSelectionProcess Context triple: [St. Elmo, memberSelectionProcess, selective tap process]
-
A.
selectionProcess
chosen
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
B.
qualificationProcess
Indicates the process or set of steps through which an entity is evaluated and approved as meeting required qualifications or standards.
-
C.
jurySelectionMethod
Indicates the process or criteria used to choose individuals who will serve on a jury.
-
D.
winnerSelectionMethod
Indicates the process or criteria used to determine which participant is chosen as the winner.
-
E.
membersAreElectedIn
Indicates that the members of a group or body attain their positions through an election process held within a specified context or jurisdiction.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fccafec8190a340356d5bbd3cdf |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.