Triple
T29986603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calc |
E761749
|
entity |
| Predicate | hasNameInSuite |
P194608
|
FINISHED |
| Object | LibreOffice Calc |
—
|
NE NERFINISHED |
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: LibreOffice Calc | Statement: [Calc, hasNameInSuite, LibreOffice Calc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInSuite Context triple: [Calc, hasNameInSuite, LibreOffice Calc]
-
A.
containsSuite
Indicates that one entity includes or encompasses a suite (a set or collection of related items, components, or units) as part of its contents.
-
B.
alsoInSuiteWith
Indicates that one entity is part of the same suite, set, or grouped collection as another entity.
-
C.
hasSuiteLevel
Indicates that one entity is associated with a specific floor or level within a suite or multi-level unit.
-
D.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
E.
hasTestNamedAfterHer
Indicates that a person is the namesake of a test, meaning a test is named in honor of or after her.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
| PDg | Predicate description generation | batch_69fd7e35967081909f8bc8389d976ffd |
completed | May 8, 2026, 6:09 a.m. |
Created at: April 29, 2026, 6:36 p.m.