Triple
T35142185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGroupBox |
E1014722
|
entity |
| Predicate | typicalChildren |
P206849
|
FINISHED |
| Object | TEdit |
—
|
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: TEdit | Statement: [TGroupBox, typicalChildren, TEdit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalChildren Context triple: [TGroupBox, typicalChildren, TEdit]
-
A.
childrenWith
Indicates that two or more entities share one or more children together as parents or guardians.
-
B.
childInFamily
Indicates that one entity is a child member within the family unit defined by the other entity.
-
C.
childrenFounded
Indicates that the subject’s children established, created, or founded the object entity (such as an organization, institution, or project).
-
D.
childrenReceive
Indicates that one or more children are the recipients of something (such as an item, benefit, or message) from another source.
-
E.
childrenStatus
Indicates the relationship describing whether and how an entity has children, including their presence, number, or relevant child-related status.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.