Triple
T28996640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Location HTTP header |
E736182
|
entity |
| Predicate | mayBeRelativeIn |
P175663
|
FINISHED |
| Object | RFC 7231 and later |
—
|
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: RFC 7231 and later | Statement: [Location HTTP header, mayBeRelativeIn, RFC 7231 and later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeRelativeIn Context triple: [Location HTTP header, mayBeRelativeIn, RFC 7231 and later]
-
A.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
B.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
C.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
D.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
E.
hasRelativeInCast
Indicates that an individual has a family member who is part of the cast of a given production.
- F. None of above. chosen
Provenance (4 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 28, 2026, 9:31 a.m.