Triple
T6519623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRW |
E148347
|
entity |
| Predicate | supportsResultFormat |
P63092
|
FINISHED |
| Object | XML records |
—
|
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: XML records | Statement: [SRW, supportsResultFormat, XML records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsResultFormat Context triple: [SRW, supportsResultFormat, XML records]
-
A.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
B.
supportsForm
chosen
Indicates that one entity provides compatibility or backing for a particular form, format, or type associated with another entity.
-
C.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
D.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
supportsForms
Indicates that one entity is capable of handling, accepting, or working with specific forms or form types associated with 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac11d0e481908103c4b51de9521e |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.