Triple
T13203616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOS |
E314300
|
entity |
| Predicate | hasThreePartStructure |
P108499
|
FINISHED |
| Object | start group of three dots |
—
|
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: start group of three dots | Statement: [SOS, hasThreePartStructure, start group of three dots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThreePartStructure Context triple: [SOS, hasThreePartStructure, start group of three dots]
-
A.
hasTwoPartStructure
Indicates that something is composed of exactly two distinct, structured parts that together form a whole.
-
B.
hasThreeVolumeStructureRole
Indicates that an entity participates in or fulfills a role within a three-volume structural organization or framework.
-
C.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
D.
hasStringParts
Indicates that a whole string is composed of, or can be decomposed into, one or more constituent string segments or parts.
-
E.
hasLogicalStructure
Indicates that one entity possesses or exhibits a specific underlying logical organization or pattern defined by another entity.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9961a48190a1157df47f59b7af |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:17 p.m.