Triple
T27591975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPIRE |
E699805
|
entity |
| Predicate | usesIdentifierFormat |
P100200
|
FINISHED |
| Object | SPIFFE ID |
—
|
NE NERFINISHED |
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: SPIFFE ID | Statement: [SPIRE, usesIdentifierFormat, SPIFFE ID]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIdentifierFormat Context triple: [SPIRE, usesIdentifierFormat, SPIFFE ID]
-
A.
supportsIdentifierType
chosen
Indicates that one entity is capable of recognizing, handling, or working with a specified type or format of identifier.
-
B.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
C.
citizenIdentificationFormat
Indicates the specific structure or standard format used for representing a citizen’s identification information.
-
D.
identificationNumberFormat
Indicates the specific structural pattern or rules that an identification number must follow.
-
E.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:05 p.m.