Triple
T26254337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Held group |
E656678
|
entity |
| Predicate | hasTripleCover |
P179187
|
FINISHED |
| Object | 3.He |
—
|
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: 3.He | Statement: [Held group, hasTripleCover, 3.He]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTripleCover Context triple: [Held group, hasTripleCover, 3.He]
-
A.
isDoubleCoverOf
Indicates that one object serves as a two-to-one covering of another, such that each point or element of the second is covered by exactly two corresponding points or elements of the first.
-
B.
hasTrilogy
Indicates that an entity is part of, or associated with, a specific trilogy within a larger set of works or narratives.
-
C.
doubleCoveredBy
Indicates that an entity is fully covered or overlapped twice by another entity or pair of entities, such that it is included in two distinct covering relationships.
-
D.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
E.
hasCoverFeature
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 26, 2026, 9:08 p.m.