Triple
T11547191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soulbinds system |
E273801
|
entity |
| Predicate | expansionLifecycle |
P30392
|
FINISHED |
| Object | primary in Shadowlands era |
—
|
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: primary in Shadowlands era | Statement: [Soulbinds system, expansionLifecycle, primary in Shadowlands era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionLifecycle Context triple: [Soulbinds system, expansionLifecycle, primary in Shadowlands era]
-
A.
expansionStatus
Indicates the current state or phase of growth, enlargement, or extension of something relative to its previous or intended size or scope.
-
B.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
C.
laterExpansionCompletion
Indicates that the completion of an expansion occurs at a later time than another referenced event or expansion.
-
D.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
E.
lifecycleType
chosen
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.