Triple
T14316956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REL |
E354981
|
entity |
| Predicate | underlyingCompanyServes |
P106227
|
FINISHED |
| Object | legal sector |
—
|
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: legal sector | Statement: [REL, underlyingCompanyServes, legal sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyServes Context triple: [REL, underlyingCompanyServes, legal sector]
-
A.
underlyingCompany
Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
-
B.
servesCompany
Indicates that one entity provides services or performs duties in support of a company.
-
C.
underlyingCompanyService
Indicates that one entity functions as a foundational or supporting service for another company or business entity.
-
D.
underlyingCompanyType
Indicates the classification or category of company that forms the basis or source for another related entity or instrument.
-
E.
underlyingCompanyBusinessDescription
chosen
Indicates the detailed description of the primary business activities or operations conducted by the underlying company.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8838e45c819080ee69dd39e3bd43 |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.