Triple
T17097376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LG Group |
E414882
|
entity |
| Predicate | isFamilyControlled |
P4852
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LG Group, isFamilyControlled, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFamilyControlled Context triple: [LG Group, isFamilyControlled, true]
-
A.
familyControlled
chosen
Indicates that an entity is owned or effectively governed by one or more members of the same family, who hold decisive control over its decisions or operations.
-
B.
isFamilyFriendly
Indicates that something is suitable for all ages and does not contain content inappropriate for children or sensitive audiences.
-
C.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
-
D.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
E.
allowsForFamily
Indicates that one entity enables or makes it possible for another entity to support or include family-related participation, benefits, or involvement.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfe92988190aa066745ca9791d5 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.