Triple
T17557429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HAL (Hypertext Application Language) |
E427622
|
entity |
| Predicate | definesSection |
P63051
|
FINISHED |
| Object | _links |
—
|
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: _links | Statement: [HAL (Hypertext Application Language), definesSection, _links]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSection Context triple: [HAL (Hypertext Application Language), definesSection, _links]
-
A.
sectionDefines
chosen
Indicates that a specific section formally specifies, describes, or establishes the meaning, rules, or scope of another element or concept.
-
B.
sectionType
Indicates the specific kind or category of section that an entity belongs to or represents.
-
C.
governsSectionOf
Indicates that one entity has authoritative control or regulatory oversight over a specific section or part of another entity.
-
D.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
E.
appliesToSectionOf
Indicates that something is relevant or applicable specifically to a particular section or subsection of a larger whole.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562413d08190acaa5272046d3626 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.