Triple
T29503813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic |
E748454
|
entity |
| Predicate | credentialReuse |
P5661
|
FINISHED |
| Object | clients may reuse credentials for same realm |
—
|
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: clients may reuse credentials for same realm | Statement: [Basic, credentialReuse, clients may reuse credentials for same realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: credentialReuse Context triple: [Basic, credentialReuse, clients may reuse credentials for same realm]
-
A.
similarCredentialAs
Indicates that one credential is considered equivalent or closely matching another in terms of content, level, or recognition.
-
B.
usedPass
Indicates that one entity has utilized or redeemed a pass, ticket, or similar authorization instrument.
-
C.
usedPassword
Indicates that one entity has employed or entered another entity as a password for authentication or access.
-
D.
keyReuse
chosen
Indicates that the same key is used multiple times, rather than being uniquely generated or dedicated for a single use or context.
-
E.
identityIssue
Indicates that an entity is experiencing uncertainty, conflict, or problems related to its sense of identity or self-definition.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c34a370819089a89f26857d3dfa |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 4:26 p.m.