Triple
T21139426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brugmann's law |
E520890
|
entity |
| Predicate | resultsInSegment |
P143011
|
FINISHED |
| Object | Indo-Iranian *ā |
—
|
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: Indo-Iranian *ā | Statement: [Brugmann's law, resultsInSegment, Indo-Iranian *ā]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultsInSegment Context triple: [Brugmann's law, resultsInSegment, Indo-Iranian *ā]
-
A.
operatesInSegment
Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
-
B.
hasSegmentOn
Indicates that one entity includes or occupies a specific segment or portion on another entity (such as a line, path, or sequence).
-
C.
returnSegment
Indicates that an entity represents a segment or portion of a return, such as a specific leg, phase, or component of a return process or journey.
-
D.
hasSegmentWith
Indicates that an entity contains or includes at least one segment that satisfies a specified condition or matches a given segment.
-
E.
segmentCovered
Indicates that one segment or portion of something is fully or partially covered or spanned by another.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235e389881908813909e05d1413a |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:57 p.m.