Triple
T27662148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XML API |
E697148
|
entity |
| Predicate | supportsHeader |
P203
|
FINISHED |
| Object | x-goog-meta-* for custom metadata |
—
|
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: x-goog-meta-* for custom metadata | Statement: [XML API, supportsHeader, x-goog-meta-* for custom metadata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHeader Context triple: [XML API, supportsHeader, x-goog-meta-* for custom metadata]
-
A.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
supportsTag
Indicates that one entity is capable of recognizing, handling, or being associated with a specified tag.
-
C.
supportsBody
Indicates that one entity physically or structurally holds up, bears the weight of, or provides foundational stability for another entity’s body.
-
D.
supportsSection
Indicates that one entity provides structural or functional backing or reinforcement to a specific section of another entity.
-
E.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: April 27, 2026, 2:37 p.m.