Triple
T28996633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Location HTTP header |
E736182
|
entity |
| Predicate | semanticsDependOn |
P74447
|
FINISHED |
| Object | status code |
—
|
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: status code | Statement: [Location HTTP header, semanticsDependOn, status code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semanticsDependOn Context triple: [Location HTTP header, semanticsDependOn, status code]
-
A.
hasSemanticsDefinedBy
chosen
Indicates that the meaning or interpretation of one entity is specified, constrained, or determined by another entity.
-
B.
hasSyntaxInfluenceFrom
Indicates that the syntax of one entity is influenced, shaped, or derived from the syntax of another entity.
-
C.
languageDependency
Indicates that one entity’s behavior, interpretation, or validity depends on or is constrained by a particular language or linguistic system associated with another entity.
-
D.
conceptuallyDependsOn
Indicates that one entity’s definition, validity, or understanding relies on or is grounded in the concepts provided by another entity.
-
E.
semanticsDetail
Indicates a more specific or fine-grained semantic characterization or nuance of a broader meaning or interpretation.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fb6ef4881909a758c3538fdec03 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:31 a.m.